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.
Hello,
Have you try the new version Windows 10 update 20H2
I have installed it on a computer this afternoon, mounted shared drive, did an offline sync on one folder and restart -> no crash.
I'm on domain and logged with a domaine account without connexion on Internet or local.
I did the test on a new computer who have never crashed before. I can't try on computers who get this problem for the moment.
I see also that icone of synchronized files have change.
Someone can try also ?
I have been working with MS on this issue for well over a month will no progress or information being shared by them. This was the latest response that I received from MS this morning; which I very aggressively denied their request.
FROM MS
"I would like to inform you that based on the review made by our Escalation Team, they said that a fix is forthcoming, and it is currently schedule to be release the 3rd week of November 2020.
Please let us know if it is ok with you to temporary archive the case, since this known issue would be fixed the 3rd week of November 2020."
Microsoft, you are really great! After 5 months you already acknowledged the problem! After 5 months of beta testing on company users. And you are going to fix it – yet you do not know if it will take one months or four - but future is bright.
I hope our lives do not depend (much) on your technology, Microsoft.
Thank you for nothing.
Afraid I can't share it, as it is only a private fix (KB900931) that was used for testing with an expiration on it. Plus you need to enable test signing for the boot config and turn Secure Boot off for it to install.
It's not meant for production environments.
what is that Private fix from Microsoft support?? will you able to share it ??
