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.
I have an active case open with MS case# 120100124004769 and a "fix" was promised the 3rd week of November which obviously didnt happen or else I would have shared. I am pushing for updates frequently but keep getting the run around. This is the most disappointed I have ever been when it comes to MS support. For us the issue comes and goes and can be at boot or sometime after login but a blue screen is sure to come at some point.
Microsoft has stated there will be no 3rd week releases (also known as "Preview release") for the months of November and December.
This means we have to wait for the normal December updates before the promised fix is available.
Hi,
I've installed KB4586853 today and it seems to have resolved the issue.
I can now build, capture and deploy a Windows 10 Education x64 20H2 image with all my GPOs (including mapped drives and enabling offline files) in place.
Thanks,
Matt
This update KB4586853 appears to have resolved our issues also. only a few machines so far, but its looking good. All previous GPO and drive mappings now working as expected.
many thanks
Hope it sticks!
From November 30, 2020—KB4586853 (OS Builds 19041.662 and 19042.662) Preview (microsoft.com):
The 0x27 reference looks promising...but what follows doesn't sound like our problem. In fact, what follows "0x27" doesn't make much sense at all to me.
I think all of our devices are probably "in the domain". Mine certainly are.
