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

I can read every message, but yes, problem with domain login when at home, doesn't matter connected or not (there is no domain)

Offline files is enabled, but I left it enabled.

What I noticed this far, when changing from a Office domain connected environment to a home not connected environment at startup and strangely other way around also, so maybe that is caused from wireless to wired. I've this BSOD.

I created simple local account (of course without offline files), before changing environment or after blue screen (BSOD), I login to this local account first, logout and login to domain account. Problem gone.

Now my question : Can I create something in maybe task scheduler, which does this job for me before login?

We've been able to re-enable Offline Files.

We had this problem with 4 of 10 v2004 PCs. With one, the user could log on without BSOD'ing but it would BSOD upon browsing a network drive. The rest BSOD'd during logon until I disabled Offline Files via remote registry edit. The other 6 are getting along just fine so far.

In all 4 cases, we've worked around it by resetting Offline Files (create a FormatDatabase DWORD value set to 1 in HKLM\System\CurrentControlSet\Services\CSC\Parameters, re-enable Offline Files service and reboot the computer). Then the users can log on with Offline Files enabled.

However, the mapped drive (which maps to a DFS share, if that's relevant) is inaccessible after logon. The workaround for that has been to add a logon script that unmaps the drive, then remaps it to the non-DFS share. Initially, only the redirected folder share (also DFS) is browsable. Later, the rest of the DFS shares become browseable, perhaps after they're onlined by Offline Files.

Small sample size. Don't know how universal this workaround is, but hope it helps somebody!

Thanks for this tip, I've just managed to re-enable offline files on one of my PCs by following this. Weirdly though, File Explorer won't resolve the name of the device where the share is hosted - I can ping it by name and I can access other shares by name, but I've had to change my shortcuts to use the IP address instead.

@LYoungESP: That's consistent with Offline Files having offlined the share. By using a "server name" for which Offline Files doesn't have anything cached, you regain access. I think that's what I'm seeing with my DFS shares, too.

There's a Microsoft script, CSCtransition.vbs, that lets you force a share online. Next time I visit my affected site I want to see if it helps (or causes blue-screens). If it helps, that's a much better workaround than accessing the same data through a different route. As soon as CSC caches data from the alternate UNC, it will likely start offlining it the same way.

This is where the script is documented: https://support.microsoft.com/en-us/help/2610379/the-folder-redirection-policy-does-not-work-if-a-previous-user-sets-a

I am having the same issue in our organisation. logging in when a computer is using offline files, and has been updated to version 2004 results in a blue screen referencing MRXSMB20.sys and a bug check of RDR_FILE_SYSTEM.

If I log in to another profile (Without a file share synced for offline use) and disable Offline files, I can log in to the original profile successfully.

It seems the 2004 version of Windows has issues with the Offline files DLL's (MRXSMB20.sys, and others). Offline files remains unusable, and this update has to be "Paused" for us until this is fixed. I have logged a bug on the feedback hub (https://aka.ms/AA9nybd) and attached the memory dumps from the BSOD.

Disabling offline files, or disconnecting from the network (Where the share it is trying to sync offline is present) is the only way to get in to the profile.

@JVR_805

Yes exact and thats why we lower down to 8ms to be faster in offline mode and system does not try to connect to servershare and will so use direct after 8ms the offline cache data.  

Point is that when now LAN... WLAN or any connection to Server comes back...  and its slower than 8ms, the drive stay offline until you force a sync on the affected drive (red x) as this also depends on the mesured network actual latency to the server as we see.

So probaby for other networks is a higher parameter to use and test here, in our environments a 32ms will show bluescreens as reported.

The switching from online to offline mode with cached domain logon with airplane mode, no LAN, no WWAN, no WLAN seems here too late happening, as we have seen in dmp file and therfore lowering this to 8ms gives faster offline mode engagement.

When we have even any LAN, WAN or even a WWAN connection in place before we logon...  the ad user logon was possible with offline files  enabled with no bluescreen.

So depency here for us to have seen this bluescreen was Airplane mode... (NO LAN cable connected, NO WLAN connected, NO WWAN connected) when domain login occures. 

Therfore is this a workaround and not a permanent solution, but we need the offline files running on any version on Windows 10 in any state 

Note that also Reset of CSC was tested alone, but unfortually has not helped us to solve this problem in airplane mode on cahce domain login.

Thx to help here to find a solution this workaround works now since more than one week on the affected devices with Win 10 OS 2004 and patched as per yesterday in additional.