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

(first time posting, so if I did something wrong I apologize)

I have the same issue with a Dell Precision M6800. I can log into our work domain (Windows Server 2012), but when I tried to work from home yesterday, I got the BSOD after hitting enter at login. No matter if I'm on my home network (wifi or wired) or not, I still receive the BSOD. I tried rolling back updates, but as everyone else has pointed out that did nothing. We have two positive Covid cases in an office of 15 so working at home is pretty important to me at the moment. 

There was another thread similar to this back in October of 2019 from Bula1 :

https://answers.microsoft.com/en-us/windows/forum/all/bsod-issue/677dae23-51c3-41ad-af92-286030ed47bc?page=2

Towards the end of the second page AndreiCN posted the following, but no one followed up on whether this worked or not.

Hi Joaquin,

KB4535996

It was fixed:

Addresses a timing issue that may cause stop error 0x27 in mrxsmb20!Smb2InvalidateFileInfoCacheEntry. This issue occurs when you rename or delete files that have certain extensions and are stored on a network share that has client-side caching enabled.

Have a good one.

With the laptop logged into the domain using ethernet cable (wifi off), I was able to put it to sleep, and then boot it back up off the network (ethernet pulled). It shows all the network drives being disconnected, including the offline/syncing drive, but I am still able to get to the offline files. I never tried to open something and resave it back though.

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.

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?

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.