This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
In my case, after modifying the registry, I still have BSOD on my first connection attempt (an account logging to the domain of my establishment). On the other hand, I manage to open my session on the second attempt.
Then, when I do not reconnect to my institution's network, I can log in on the first attempt.
I have not yet tested the reconnect to the domain since the KB4580364 and KB4586781 Windows updates today.
In my case I'm able to log into the PCs, either with a local account or disconnecting the Ethernet cable and turning off WIFI before entering the credentials.
ps: I tested with 20H2 same results..
Was this the update that was supposed to fix it? You would need 2004 already installed before you can install this update. A few of our PCs we couldn't even get logged into because of the BSOD. Curious how they are going to fix this. If they update the version prior, or we get a new 2004 upgrade installer?
I installed today's fix KB4586781 - Build 19041.630 and the problem still persists.
And in parallel to that, Microsoft is hardly pushing to get Windows 2004 installed to all my other machines with Offline Files enabled. Which I am preventing by Group Policy.
Dear Microsoft, thank you for nothing! You are darn idiots.
Are you waiting for anniversary of this bug? Or what?
I have loaded an evaluation build 20241 and have been able to login and not get the BSOD with
OS Build 20241.1008
Experience Windows feature Pack 120.27500.3.0
