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

Anonymous
2020-06-08T14:50:36+00:00

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.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

167 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-09-25T14:09:02+00:00

    Several of my clients are having this issue I knew it's to do with folder redirection as logging into local profiles wouldn't cause this. this is frustrating a ton of people. Hope MS gets their act together and releases a hot fix ASAP.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-23T09:01:23+00:00

    did MS acknowledge the problem (bug)? because i dont see any reply from microsoft tech team!!?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-22T11:24:15+00:00

    So far for me the easiest workaround has been to keep offline folders and folder redirection enabled but to exclude users with Windows 10 2004 builds from mapping a driveletter to their homedrive / homefolder

    I use Group Policy Preferences for drivemappings and have enabled item level targeting for this.

    It only maps a drive letter if:

    The string registry value at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuildNumber does not exist or does not have a value data 19041

    • Since Folder redirection and offline files still works, users can still access their redirected folders either directly in Explorer (Documents is for example mapped to \server\share%username%\Documents)
    • They can access their homedrive root via UNC path: \server\share%username%. A simple shortcut to that will suffice.

    For my users the negative impact of not being able to access their homefolder via driveletter is relatively low and it's easy to implement and rollback. The same could be done with a logonscript.

    Perhaps once you would need to reset the CSC cache for users that are already affected and get BSOD at logon (like I have)

    Alternatively try having them log on "offline", then connect to network, remove driveletter/disconnect drive and run gpupdate /force. Logoff and back on.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-21T15:19:33+00:00

    I concur the 20H2 did not resolve the issue

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2020-09-21T15:13:15+00:00

    I installed the then current build of 20H2 back in August; it definitely did NOT fix the problem. I’m still running 1909 with newer Feature Updates blocked.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments