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

I just wanted to add my experience of this - I use 3 or 4 machines which are updated to build 2004, both domain and standalone, with different folder redirections synced. I've only had the BSOD at login on one desktop PC so far, and I'm not sure why this one would be affected while the others aren't. Thanks to this thread I managed to get round the fault by going into safe mode and disabling offline file sync in the registry. As this is a desktop machine there isn't any real problem doing this, as I don't need these files outside the office.

As a domain user I don't have the local admin password to try that workaround, but before getting into safe mode using my cached domain credentials, I got the BSOD whether I was connected to the LAN or not. Also, I am not sure how long after installing 2004 the fault appeared (the PC was switched off for a couple of weeks), but it wasn't immediate - suggesting an update is responsible.

I hope MS are taking note of this and working on a fix...

If you have the problem "log on is only possible with an active network connection to your domain" the following worked for me.

Workaround:

You need one local account not in the network domain and of course no offline files connected for this account

If you have the local account created and you are now NOT connected to the domain or a network

• start the PC
• logon with the local account, for me it is my local admin account.
• wait until the start up has finished
• go to the Windows Logo in the taskbar and right click with the mouse
• select the "Shutdown or Log Off" menu (I have a German version if the translated wording in different for you :-))
• LOG OFF from the local account
• LOG ON with your domain account and I, hopefully you are also, do not run into the BSOD and can work with the synchonized files.

Best thing I can recommend if possible is to disable offline files and try that if you do not rely on them. Disconnected ethernet, or wireless, log in with cached domain profile, disable offline file sync and try to reconnect to the network and reboot. This has been the best resolution I have seen for right now if you cannot roll back from other people having the issue I posted about in my OP and I have tried on numerous machines of my own and they are working for now with this bandaid on. As to the "opposite" issues other people are experiencing where they can log on ONLY on a network, I do not know about that as I have not seen it and had opposite effects for why I originally posted this.

As to when you will see a fix? Who knows, in my last post I posted the link to the known issues from microsofts website and I do not see anything related to this mentioned there and people have tried latest updates and test builds without luck.

I am having same experience with BSOD with Windows 10 Build 2004, RDR FILE SYSTEM, mrxsmb20.sys, folder redirection to server (WSE2016) and offline files enabled.  I can log onto a local account without crashing but using a domain account will crash it almost everytime.  I don't have the option of reverting to the prior build since too much time has elapsed since I updated to build 2004.  Debating whether to rebuild the system using Dell OS Recovery Tool.  Pain in the butt.  I may wait for a fix but the question is how long will I have to wait?

It seems odd to me that there seem to be 2 opposite issues here providing the same error.

My original post was about how machines connected to a network will BSOD when logging in, but will not when not connected to a network, however I feel like this thread has evolved into a whole section of people who are having almost the same issue, and receiving the same BSOD however are having the entirely opposite problem of my initial issue. For these people their computer seems to BSOD ONLY when it is NOT connected to a network, but if they are connected they can log in. 

Seems very odd to me that the issues are so similar, yet literally could not be more opposite of each other, what is causing one to work off the network yet the other ones to only work on a network? In my experience the only thing that has temporarily resolved these problems for us was disabling offline file sync and the PCs can stay on the network.

Is the issue with Microsoft, or is there some other underlying issue on everyones servers that would be causing one bug for some people and the opposite bug for other people? I have seen absolutely 0 mention of this issue from Microsoft, no comment about it under their known issues for this build https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004 . So when will this be acknowledged, or at least responded to that it's an issue on the backend somewhere and not with their build?

It has been 2 months since this build came out and these issues have started and we are forcing clients to be on older versions of the OS, or being forced to disable offline file sync which hinders their ability to work on a laptop etc when not on site, or in event of ever losing a domain connection for whatever reason they would no longer have access to any of their files. At least acknowledge the issue and add it to your list of known bugs Microsoft.