rdr_file_system 0x27 BSOD After Windows 10 2004 update, but only on domain profiles

Good morning, I am having an issue on some PCs recently after some PCs received the Windows 10 2004 build update. After receiving said update, the machines will BSOD with a 0x027 error code when logging into a domain profile while connected to the network.

If I remove the network cable from the PC and log into a domain account that was cached on the machine before the update, it will log in without issues and then I can connect it to the network and it seems to resume function. I can also sign into a local account on the machine, with and without network connectivity. 

I used Bluescreen View to look at the dumps which seem to be showing rdbss.sys and mrxsmb20.sys as drivers that are causing the issue. I have tried updating network drivers etc from the vendors websites and not relying on Windows to, but am still having the issue.

The other bizarre thing is if the PC crashes 3 times, boots into the recovery mode to try and repair your PC and I restart it, it will then log in once to a domain account and seem to be functioning, however if the PC is restarted it will BSOD on log in.

Has anyone seen or heard of any issues like this since this update? Could it be something out dated on the server that is causing the issue to happen to the machines on the newer OS? I can't help but feel like it has something to do with folder redirection and that is why cached accounts will work with no network connection however I am stumped how to get around this other than not updating every other machine, and rolling back if possible (I had a PC that was upgraded from Windows 7 to 10 and went straight to the 2004 build and BSOD'd, I tried to roll back to Win7 and system will not boot at the moment saying it is missing system files etc.).

I have some mini dumps I can share if that would help as I would like to get to the bottom of this if possible.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Tip is to try this that seem to have helped. (havent had any test case yet though) 

https://www.reddit.com/r/sysadmin/comments/ipno8v/windows_10_x64_2004_19041450_offline_files_bug/g57vn0s/?context=3

4 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes, it seem's to work 💪

I hope it will work well in next few days...

I will tell you in next days.

Thanks!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I checked on one of the affected computers and it already had the registry DWORD "ProviderFlags" and it was already set to 1.

In my case, I tried logging in with no network and didn't get the BSOD, then restarted and plugged in the network and logged in before the network was ready and got the BSOD.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

In precision : Create the registry DWORD "ProviderFlags" and set it to 1 for each offline-synced network drive (a letter) under HKEY_CURRENT_USER\Network (this enables SMBv1 on client for those drives)! Check which drive is synced/connected!

See also https://www.winhelponline.com/blog/mapped-network-drives-fix-windows-10-v2004/

 

jPNRgc

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

My bigger concern there would be using SMBv1. Any port in a storm, I guess. Speaking of which...

This should be solvable/avoidable/workaroundable for OneDrive for Business users by redirecting folders into %OneDriveCommercial% (or a subfolder thereof). That can be done by the usual Folder Redirection GPO, or if Documents, Desktop & Pictures are all you care about, by the OneDrive GPO. Then no Offline Files are involved (at least for Known Folders). Discussion about that here: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_onedrivefb-mso_win10-mso_o365b/odfb-known-folders-vs-group-policy-folder/db89d0a5-e02b-4fe4-9432-c86404d70003

If you're going that direction anyway (I am at one 2004/Offline Files-afflicted client that also wants to do away with their file server), this might be the time. Might need to follow it up with one, last Offline Files cache reset, or else disable the service by GPO.

Since we don't know how long it will take Microsoft to fix it since they haven't even published that the bug exists, expect it to take a while. (Well, I think we're already beyond "a while"!) Therefore, I'm also toying with using this for other sites that have no plans to eliminate their file server but use ODfB.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

... it already had the registry DWORD "ProviderFlags" and it was already set to 1. ...

In addition to setting the ProviderFlags, it seems to me that the following setting in the Windows firewall is necessary:
Enable ports 137, 138, 139 and 445 in the private network in the Windows firewall.
Since then, the BSOD has disappeared when I log into the local network with the use of offline files, regardless of whether my old faithful Buffalo is on or off.
Tested on two systems (HP ProDesk and Lenovo Notebook, with a Buffalo LS-WSXL in a workgroup).

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Not sure if someone has mentioned this before, but are you able to log in via RDP? We have had this issue with some of our users, and it's been real hit or miss, and then it dawned on me: with all the working from home due to covid, a lot of our users are using RDP to connect to their PCs in the office. So, I decided to test this theory. I am in the office, and when I try to log in at the PC, it blue screens repeatedly. But if I RDP in via another computer, I am able to log in. Then, at the PC I can login to that session, thus terminating the remote connection, and remain logged in with no blue screen.

I know this isn't a fix, but if other people can replicate it, maybe it will help us get a better grasp on what's going on.

Can anyone else confirm this works for them?

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Ive been getting lots of calls from clients having temp profile login and roaming profiles breaking. Had to rebuild several accounts so far.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Morning,

Same problem here, BOD continues in machines. 

Please microsoft Fix this with one update.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

... but are you able to log in via RDP? ...


I can log into my computer from my laptop with RDP. The reverse is also possible. There never was a BSOD.
In my estimation, the error occurs when offlinefiles are activated and configured and/or when a network component requires SMB1 and the firewall is blocking the old Netbios ports.
At least it helped on my local network:
- ProviderFlags DWORD 32Bit to 1 for each individual share in "HKEY_CURRENT_USER \ Network"
- In the private network of the Windows firewall, release ports 137-139, 445 for NetBios and SMB, TCP and UDP incoming and outgoing.

In my opinion there must be a bug in the timing with SMB1 and the login, in which a module of the RDR_FILE_SYSTEM, with deactivated SMB1 then when processing mrxsmb20.sys and with activated SMB1 then when processing mrxsmb10.sys, the BSOD triggers the user login.
In the end, only Microsoft itself will know where the trouble is and at some point there will be a small fix in the major updates ...

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated December 1, 2020 Views 18,352 Applies to: