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.
So far the only option in my environment is to rollback to to 1909, but now after we rollback we are getting a DLL error with some applications including Adobe:
C:\windows\system32\msvcp140.dll is either not designed to run on Windows or it contains an error. Error status 0x000012f
has anyone gotten this? any suggestions?
I concur the 20H2 did not resolve the issue
I installed the then current build of 20H2 back in August; it definitely did NOT fix the problem. I’m still running 1909 with newer Feature Updates blocked.
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
I am still having the exact same problem, even after installing the two updates released today (KB4565503 & KB4566785).
I don't have much to add other than the following:
The server that the redirected folders reside on is rather old, running Windows Server 2003.
Also, on the offending computers, I notice a NETLOGON error in the event viewer. Details are:
Event ID 5719
This computer was not able to set up a secure session with a domain controller in domain XXXXXXX due to the following:
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
I have no idea if these are related or not, but it seems like too much of a coincidence. The domain controllers are up and available, and applications that use AD authentication work just fine, however offline files remain disconnected, and network shares are disconnected as well. However, using an IP address in the UNC will allow them to authenticate and connect.
Computers still running build 1909 are completely unaffected, and rolling back to 1909 fixes the problem, as stated before. Luckily I have a few computers I don't desperately need to roll back that I can play with at least up until the rollback window expires (I bumped it out to 30 days), if anyone has any ideas.
