File explorer crashes when opening WSL folders in Windows 11

alex180500 commented 2 years ago

Version

Windows 11 [10.0.22000.348]

WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version

5.10.74.3

Distro Version

Ubuntu 20.04

Other Software

wsl --version

WSL version: 0.50.2.0
Kernel version: 5.10.74.3
WSLg version: 1.0.29
Windows version: 10.0.22000.348

Repro Steps

Just opening the "Ubuntu" folder in File Explorer.

Expected Behavior

Should open the folder.

Actual Behavior

1 out of 3 times File Explorer just become unresponsible and crashes, using the WSL terminal in the meantime works without any issue.

Diagnostic Logs

No response

lediur commented 2 years ago

I wonder if this is related to an issue I'm seeing as well #7773

alex180500 commented 2 years ago

I think it is, I get your same problem when opening files using any windows software on wsl files (also this behaviour is kind of randomic, it works about 1/3 of the times)

Venorcis commented 2 years ago

I'm experiencing this on Windows 11 for a week or two now as well, with the WSL Preview version. Seemingly randomly but mostly after a few hours of working, the WSL drive becomes completely incessible from Windows (only the WSL terminal still works). AFAIK only a reboot can resolve it, really annoying.

benhillis commented 2 years ago

I'm having trouble reproducing this locally. If somebody could help narrow down how things get to this state it would be very helpful.

alex180500 commented 2 years ago

Access to the files via any mean, open windows file explorer and move files, open a file using any windows app. Close it.
Wait 5 minutes
Open file explorer again and try opening the WSL folder
Enjoy the crash

jsquire commented 2 years ago

I'm having trouble reproducing this locally. If somebody could help narrow down how things get to this state it would be very helpful.

@benhillis: Opening a non-trivial project in Visual Studio from the WSL filesystem and then running the debugger is a trigger for me ~75% of the time. The build typically runs normally and then the debugger attach and symbol loading have a massive slow-down. After, just about any activity via the //wsl$ share will start to hang. Often, just working in Visual Studio against source on the WSL filesystem and saving files frequently will randomly cause the hang as well.

The last time it happened, I noticed the following, though I'm not sure if it has any significance:

>> dmesg | grep 9p                                                         

[    0.867422] 9p: Installing v9fs 9p2000 file system support
[    0.869883] FS-Cache: Netfs '9p' registered for caching
[    1.057234] 9pnet: Installing 9P2000 support
[    2.840855] 9pnet_virtio: no channels available for device drvfs
[    2.965188] 9pnet_virtio: no channels available for device drvfs
[    3.523789] 9pnet_virtio: no channels available for device drvfs
[    3.631238] 9pnet_virtio: no channels available for device drvfs
[  538.577483] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.150688] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.152132] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.159832] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.166194] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.172368] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.177941] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.188934] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.198901] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4035.983219] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.428534] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.433433] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.441183] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.446752] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.451930] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.460326] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.464116] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.470673] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 5005.202384] 9pnet_virtio: no channels available for device drvfsa
[ 5005.354292] 9pnet_virtio: no channels available for device drvfsa
[ 5005.504846] 9pnet_virtio: no channels available for device drvfsa
[ 5015.535921] 9pnet_virtio: no channels available for device drvfsa
[ 5015.685556] 9pnet_virtio: no channels available for device drvfsa

Environment:

>> wsl --version

WSL version: 0.50.2.0
Kernel version: 5.10.74.3
WSLg version: 1.0.29
Windows version: 10.0.22000.318

Zeebzog commented 2 years ago

Same problem. Works 1 in 3 times. If crashes can only be fixed by reboot. Also since the last crash I cannot from Ubuntu start visual code by time code ., now just hangs

jsquire commented 2 years ago

Same problem. Works 1 in 3 times. If crashes can only be fixed by reboot. Also since the last crash I cannot from Ubuntu start visual code by time code ., now just hangs

This has happened to me as well. What worked for me was to do a wsl --shutdown, repair the "Windows Subsystem for Linux Preview" app, and then reboot.

The hang continues to happen, but I was able to launch code and other Windows tools from WSL again.

alex180500 commented 2 years ago

Another thing to point out is that whenever you first start the wsl, file explorer (or vscode or 9p for that matter) works all the time (at least for me), these crashes only happens after a while.

Venorcis commented 2 years ago

I'm having trouble reproducing this locally. If somebody could help narrow down how things get to this state it would be very helpful.

@benhillis: Opening a non-trivial project in Visual Studio from the WSL filesystem and then running the debugger is a trigger for me ~75% of the time. The build typically runs normally and then the debugger attach and symbol loading have a massive slow-down. After, just about any activity via the //wsl$ share will start to hang. Often, just working in Visual Studio against source on the WSL filesystem and saving files frequently will randomly cause the hang as well.

The last time it happened, I noticed the following, though I'm not sure if it has any significance:

>> dmesg | grep 9p                                                         

[    0.867422] 9p: Installing v9fs 9p2000 file system support
[    0.869883] FS-Cache: Netfs '9p' registered for caching
[    1.057234] 9pnet: Installing 9P2000 support
[    2.840855] 9pnet_virtio: no channels available for device drvfs
[    2.965188] 9pnet_virtio: no channels available for device drvfs
[    3.523789] 9pnet_virtio: no channels available for device drvfs
[    3.631238] 9pnet_virtio: no channels available for device drvfs
[  538.577483] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.150688] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.152132] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.159832] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.166194] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.172368] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.177941] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.188934] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[  541.198901] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4035.983219] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.428534] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.433433] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.441183] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.446752] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.451930] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.460326] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.464116] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 4038.470673] init: (1) ERROR: LogException:26: FS: (null) Invalid argument @D:/a/1/s/src/linux/plan9/p9protohelpers.h:142 (Name)
[ 5005.202384] 9pnet_virtio: no channels available for device drvfsa
[ 5005.354292] 9pnet_virtio: no channels available for device drvfsa
[ 5005.504846] 9pnet_virtio: no channels available for device drvfsa
[ 5015.535921] 9pnet_virtio: no channels available for device drvfsa
[ 5015.685556] 9pnet_virtio: no channels available for device drvfsa

Environment:

>> wsl --version

WSL version: 0.50.2.0
Kernel version: 5.10.74.3
WSLg version: 1.0.29
Windows version: 10.0.22000.318

For me it's roughly the same, it seems mostly working in a PhpStorm project residing on the WSL drive just randomly causes this every few minutes.

Also at that point the same behaviour as #7787 and #7371 occurs

benhillis commented 2 years ago

@jsquire - Could you enable 9p logging in your distro so I can see what's going on?

wsl.exe --shutdown
wsl -u root vi /etc/wsl.conf
Add this line:
fileServer.logFile=/path/to/log/file
wsl.exe --shutdown

And share the log file after you repro? Thanks!

ghost commented 2 years ago

Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it.

Thank you!

jsquire commented 2 years ago

@jsquire - Could you enable 9p logging in your distro so I can see what's going on?

Happy to. Is it safe to assume that the fileServer.logFile setting should go in the [automount] label in wsl.conf? That's where I've put it for now.

EDIT:
That doesn't appear to be the correct section to add it to and, unfortunately, the docs don't detail that setting. I had this enabled and just did the freeze/reboot dance and have no long to show for it.

@benhillis: I'd appreciate your insight.

Biswa96 commented 2 years ago

It should be something like this in /etc/wsl.conf file:

[fileServer]
enabled=true
logFile=/mnt/c/MyFiles/9p.log

automount and fileServer are two different sections.

marforon commented 2 years ago

It seems to only happen if you have installed WSL through Microsoft Store - https://www.microsoft.com/store/productId/9P9TQF7MRM4R. Since I uninstalled WSL as the app and installed WSL throuh wsl --install it hasn't happened yet.

Until it's fixed, it's useless. I spent lot of time with reinstalling the Windows. In my case, IDE was also freezing as it couldn't access files, very annoying.

overflowz commented 2 years ago

can confirm, it's really annoying. I also have WSL installed both via apps and features (long time ago) and through the microsoft store. I can't risk uninstalling it (I don't want my files on WSL to be removed).

marforon commented 2 years ago

can confirm, it's really annoying. I also have WSL installed both via apps and features (long time ago) and through the microsoft store. I can't risk uninstalling it (I don't want my files on WSL to be removed).

I haven't lost anything, I just had to toggle WSL feature https://pureinfotech.com/uninstall-wsl2-windows-10/. But it's not smooth change, if I wouldn't have everything backed up, I wouldn't risk it either.

jsquire commented 2 years ago

It should be something like this in /etc/wsl.conf file:
[fileServer]
enabled=true
logFile=/mnt/c/MyFiles/9p.log

Thanks, @Biswa96. The fileServer section isn't in the docs, so I didn't recognize the notation that Ben was using and assumed this was just an undocumented debugging key.

Biswa96 commented 2 years ago

I requested to document it some days ago here https://github.com/MicrosoftDocs/WSL/pull/1365#issuecomment-985221814

workeffortwaste commented 2 years ago

As mentioned above simply uninstalling the WSL Preview app from the Store and letting it fallback to the WSL version supplied with Windows 11 has resolved this issue for me.

jsquire commented 2 years ago

@benhillis: I captured logs over several hang/reboot cycles and uploaded one via Feedback Hub as requested. It was logged as bug #37313951.

Unfortunately, the logs showed nothing unusual - just accepted/connected/disconnected info messages. During the hangs, dmesg seems to consistently capture the "no channels" message that I referenced above and often the log exception as well.

To attempt to unblock myself for now, I've shifted to the Win11 built-in WSL feature and uninstalled the preview app as has been suggested by others.

overflowz commented 2 years ago

Looks like uninstalling the app from the Microsoft store also solved the issue for me.

spences10 commented 2 years ago

I've got this happening on my 'normal' Windows 11 machine also can confirm same behaviour on a new Windows 11 insiders build.

Installed Windows Subsystem for Linux Preview from the store and had the same issues with code . and explorer.exe . hanging.

I thought this was only a Ubuntu thing as using a Fedora distro I wasn't having any issues and I can have the issue happen on Ubuntu which makes it unusable I can then switch over to Fedora and use the file explorer.

spences10 commented 2 years ago

Uninstalling reinstall didn't resolve this for me.

I even tried removing the Windows store app and going via the usual method with that issue persisting.

I'm on OS build 22509.1011.

I haven't done that same trouble shooting on my 'normal' release Win 11 but the same issue with explorer.exe was on there as well.

I started using Fedora and so far haven't had the same issue on that distribution, is it an Ubuntu specific thing?

spences10 commented 2 years ago

Scratch that!

Still happens with my Fedora instance

intdel commented 2 years ago

The workaround is to remove the WSL version installed from the store as explained here: https://github.com/microsoft/WSL/issues/7754#issuecomment-990057935

DanPinGF commented 2 years ago

If you look at the C:\ProgramData\Microsoft\Windows\WER\ReportArchive folder you might find useful information for the crash(es). Just open the .WER files in Notepad.

ghost commented 2 years ago

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

alex180500 commented 2 years ago

I mean the issue hasn't been resolved, anybody needs any other information?

spences10 commented 2 years ago

The workaround is to remove the WSL version installed from the store as explained here: #7754 (comment)

This doesn't work as a workaround for me, currently I have WSL Windows feature turned off

On the insiders version I'm on it seems to install the Windows Store App automatically.

When I lose the functionality all that works is turning that feature off, or on again and it works for a while before happening again.

Quality bug report that right there ☝️ 😂

marco-pm commented 2 years ago

Same problem here, this bug was driving me crazy. In addition to WSL files being inaccessible, file explorer stops autorefreshing the directories (so I would need to manually trigger the refresh after every file copy/move/rename etc.). Luckily the temporary fix above has worked for me as well, thank you!

overflowz commented 2 years ago

Someone needs to reopen this, otherwise, it won't be tracked.

DanPinGF commented 2 years ago

@overflowz - The issue was closed by a bot and not the author, so since it can only be reopened by collaborators and team members as far as I know in this case I'd probably refer to one of them (@OneBlue).

Anyways, @alex180500, at the least can you post a WER report of your latest explorer.exe crash? It should include the exception code and faulting modules.

OneBlue commented 2 years ago

Reopening this.

Can someone with a repro share the content of HKEY_LOCAL_MACHINE\system\currentcontrolset\services\P9Np\networkprovider and collect logs ?

alex180500 commented 2 years ago

this is a report of the latest explorer.exe hang:

Version=1
EventType=AppHangB1
EventTime=132845181706284354
ReportType=3
Consent=1
UploadTime=132845181813466704
ReportFlags=524288
ReportStatus=268435456
ReportIdentifier=e729f227-d81b-451e-8c79-05d212458f67
IntegratorReportIdentifier=99010b63-26ec-4296-98fe-ea30ce6a208f
Wow64Host=34404
NsAppName=explorer.exe
OriginalFilename=EXPLORER.EXE
AppSessionGuid=00001a18-0001-0049-f1aa-02d7c3f5d701
TargetAppId=W:0000f519feec486de87ed73cb92d3cac802400000000!0000ff02a95a759c1880fc580158062d43fdf3b85739!explorer.exe
TargetAppVer=2093//06//27:17:07:21!4dba91!explorer.exe
BootId=4294967295
HeapdumpAttached=1
TargetAsId=129
UserImpactVector=269488400
IsFatal=1
EtwNonCollectReason=4
Response.BucketId=2d3b29d7ccaa8a035b2cea756310376e
Response.BucketTable=5
Response.LegacyBucketId=1958197727893403502
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=explorer.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.22000.120
Sig[2].Name=Application Timestamp
Sig[2].Value=e846e749
Sig[3].Name=Hang Signature
Sig[3].Value=31f9
Sig[4].Name=Hang Type
Sig[4].Value=134742016
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.22000.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=31f9970f27e002c92b0e6fce9462dea8
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=6ba0
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=6ba072233297623a5aaf980c0f693e40
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=31f9
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=31f9970f27e002c92b0e6fce9462dea8
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=6ba0
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=6ba072233297623a5aaf980c0f693e40
UI[3]=Windows Explorer is not responding
UI[4]=If you restart or close the program, you might lose information.
UI[5]=Restart the program
UI[6]=Restart the program
LoadedModule[0]=C:\WINDOWS\Explorer.EXE
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[5]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[6]=C:\WINDOWS\System32\combase.dll
LoadedModule[7]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[8]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[9]=C:\WINDOWS\System32\shcore.dll
LoadedModule[10]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[11]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[12]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[13]=C:\WINDOWS\SYSTEM32\AEPIC.dll
LoadedModule[14]=C:\WINDOWS\System32\sechost.dll
LoadedModule[15]=C:\WINDOWS\SYSTEM32\TWINAPI.dll
LoadedModule[16]=C:\WINDOWS\System32\shlwapi.dll
LoadedModule[17]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[18]=C:\WINDOWS\System32\user32.dll
LoadedModule[19]=C:\WINDOWS\System32\win32u.dll
LoadedModule[20]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[21]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[22]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[24]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[25]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
LoadedModule[28]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\UxTheme.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\twinapi.appcore.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\NETAPI32.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\DSREG.DLL
LoadedModule[36]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\UMPDC.dll
LoadedModule[39]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[40]=C:\WINDOWS\SYSTEM32\dxcore.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\NInput.dll
LoadedModule[42]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[43]=C:\WINDOWS\System32\ole32.dll
LoadedModule[44]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.22000.120_none_9d947278b86cc467\comctl32.dll
LoadedModule[45]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[46]=C:\Windows\System32\appresolver.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[48]=C:\Windows\System32\OneCoreUAPCommonProxyStub.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\CFGMGR32.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\apphelp.dll
LoadedModule[51]=C:\WINDOWS\system32\NetworkExplorer.dll
LoadedModule[52]=C:\Windows\System32\StartTileData.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\usermgrcli.dll
LoadedModule[54]=C:\Windows\System32\OneCoreCommonProxyStub.dll
LoadedModule[55]=C:\Windows\System32\Windows.StateRepositoryPS.dll
LoadedModule[56]=C:\Windows\System32\Windows.ApplicationModel.dll
LoadedModule[57]=C:\Windows\System32\usermgrproxy.dll
LoadedModule[58]=C:\Windows\System32\AppXDeploymentClient.dll
LoadedModule[59]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[60]=C:\Windows\System32\iertutil.dll
LoadedModule[61]=C:\Windows\System32\srvcli.dll
LoadedModule[62]=C:\Windows\System32\netutils.dll
LoadedModule[63]=C:\WINDOWS\System32\IDStore.dll
LoadedModule[64]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[65]=C:\WINDOWS\System32\SAMLIB.dll
LoadedModule[66]=C:\Windows\System32\Windows.CloudStore.dll
LoadedModule[67]=C:\WINDOWS\SYSTEM32\policymanager.dll
LoadedModule[68]=C:\WINDOWS\SYSTEM32\msvcp110_win.dll
LoadedModule[69]=C:\Windows\System32\AppExtension.dll
LoadedModule[70]=C:\Windows\System32\Windows.StateRepositoryClient.dll
LoadedModule[71]=C:\Windows\System32\Bcp47Langs.dll
LoadedModule[72]=C:\WINDOWS\system32\windowsudk.shellcommon.dll
LoadedModule[73]=C:\WINDOWS\system32\WindowsCodecs.dll
LoadedModule[74]=C:\WINDOWS\system32\XmlLite.dll
LoadedModule[75]=C:\WINDOWS\SYSTEM32\windows.staterepositorycore.dll
LoadedModule[76]=C:\Windows\System32\Taskbar.dll
LoadedModule[77]=C:\WINDOWS\SYSTEM32\winsta.dll
LoadedModule[78]=C:\Windows\System32\d2d1.dll
LoadedModule[79]=C:\Windows\System32\DWrite.dll
LoadedModule[80]=C:\Windows\System32\SLC.dll
LoadedModule[81]=C:\WINDOWS\SYSTEM32\SndVolSSO.DLL
LoadedModule[82]=C:\WINDOWS\SYSTEM32\MMDevAPI.DLL
LoadedModule[83]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[84]=C:\Windows\System32\OLEACC.dll
LoadedModule[85]=C:\WINDOWS\system32\CoreMessaging.dll
LoadedModule[86]=C:\Windows\System32\Windows.UI.dll
LoadedModule[87]=C:\Windows\System32\Windows.UI.Immersive.dll
LoadedModule[88]=C:\Windows\System32\dcomp.dll
LoadedModule[89]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[90]=C:\Windows\System32\TileDataRepository.dll
LoadedModule[91]=C:\Windows\System32\Windows.StateRepository.dll
LoadedModule[92]=C:\Windows\System32\StateRepository.Core.dll
LoadedModule[93]=C:\WINDOWS\system32\explorerframe.dll
LoadedModule[94]=C:\WINDOWS\SYSTEM32\tabbtn.dll
LoadedModule[95]=C:\WINDOWS\System32\coml2.dll
LoadedModule[96]=C:\Windows\System32\TabBtnEx.dll
LoadedModule[97]=C:\Windows\System32\wpnclient.dll
LoadedModule[98]=C:\Windows\System32\MrmCoreR.dll
LoadedModule[99]=C:\Windows\System32\SettingsHandlers_DesktopTaskbar.dll
LoadedModule[100]=C:\WINDOWS\SYSTEM32\languageoverlayutil.dll
LoadedModule[101]=C:\Windows\System32\bcp47mrm.dll
LoadedModule[102]=C:\WINDOWS\system32\twinui.pcshell.dll
LoadedModule[103]=C:\WINDOWS\system32\wincorlib.DLL
LoadedModule[104]=C:\Windows\System32\windows.immersiveshell.serviceprovider.dll
LoadedModule[105]=C:\WINDOWS\System32\twinui.appcore.dll
LoadedModule[106]=C:\Windows\System32\thumbcache.dll
LoadedModule[107]=C:\WINDOWS\system32\twinui.dll
LoadedModule[108]=C:\WINDOWS\SYSTEM32\edputil.dll
LoadedModule[109]=C:\Windows\System32\VAULTCLI.dll
LoadedModule[110]=C:\WINDOWS\SYSTEM32\textinputframework.dll
LoadedModule[111]=C:\WINDOWS\SYSTEM32\cldapi.dll
LoadedModule[112]=C:\WINDOWS\SYSTEM32\FLTLIB.DLL
LoadedModule[113]=C:\WINDOWS\SYSTEM32\TextShaping.dll
LoadedModule[114]=C:\WINDOWS\SYSTEM32\Wldp.dll
LoadedModule[115]=C:\Windows\System32\sppc.dll
LoadedModule[116]=C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL
LoadedModule[117]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[118]=C:\WINDOWS\SYSTEM32\directxdatabasehelper.dll
LoadedModule[119]=C:\WINDOWS\System32\ApplicationFrame.dll
LoadedModule[120]=C:\WINDOWS\System32\DriverStore\FileRepository\u0373733.inf_amd64_a70fcd9f085a1b58\B373745\aticfx64.dll
LoadedModule[121]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[122]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[123]=C:\WINDOWS\System32\DriverStore\FileRepository\u0373733.inf_amd64_a70fcd9f085a1b58\B373745\atiuxp64.dll
LoadedModule[124]=C:\WINDOWS\System32\DriverStore\FileRepository\u0373733.inf_amd64_a70fcd9f085a1b58\B373745\atidxx64.dll
LoadedModule[125]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[126]=C:\WINDOWS\SYSTEM32\amdihk64.dll
LoadedModule[127]=C:\WINDOWS\SYSTEM32\PhotoMetadataHandler.dll
LoadedModule[128]=C:\Windows\System32\HolographicExtensions.dll
LoadedModule[129]=C:\Windows\System32\ResourcePolicyClient.dll
LoadedModule[130]=C:\WINDOWS\SYSTEM32\ntshrui.dll
LoadedModule[131]=C:\WINDOWS\SYSTEM32\cscapi.dll
LoadedModule[132]=C:\WINDOWS\SYSTEM32\D3DSCache.dll
LoadedModule[133]=C:\Windows\System32\AboveLockAppHost.dll
LoadedModule[134]=C:\Windows\System32\Windows.System.Launcher.dll
LoadedModule[135]=C:\WINDOWS\SYSTEM32\pfclient.dll
LoadedModule[136]=C:\WINDOWS\SYSTEM32\LINKINFO.dll
LoadedModule[137]=C:\Windows\System32\wuceffects.dll
LoadedModule[138]=C:\Windows\System32\InputHost.dll
LoadedModule[139]=C:\Windows\System32\Windows.UI.Core.TextInput.dll
LoadedModule[140]=C:\Windows\System32\Windows.Web.dll
LoadedModule[141]=C:\Windows\System32\Windows.Shell.BlueLightReduction.dll
LoadedModule[142]=C:\Windows\System32\WKSCLI.DLL
LoadedModule[143]=C:\WINDOWS\SYSTEM32\msIso.dll
LoadedModule[144]=C:\Windows\System32\mscms.dll
LoadedModule[145]=C:\Windows\System32\Windows.Internal.Signals.dll
LoadedModule[146]=C:\Windows\System32\cdp.dll
LoadedModule[147]=C:\WINDOWS\system32\Windows.Internal.ShellCommon.dll
LoadedModule[148]=C:\Windows\System32\TaskFlowDataEngine.dll
LoadedModule[149]=C:\WINDOWS\SYSTEM32\Secur32.dll
LoadedModule[150]=C:\WINDOWS\System32\StructuredQuery.dll
LoadedModule[151]=C:\Windows\System32\Windows.Security.Authentication.Web.Core.dll
LoadedModule[152]=C:\Windows\System32\Windows.Data.Activities.dll
LoadedModule[153]=C:\Windows\System32\Windows.Devices.Enumeration.dll
LoadedModule[154]=C:\WINDOWS\System32\MSWB7.dll
LoadedModule[155]=C:\Windows\System32\Windows.Internal.UI.Shell.WindowTabManager.dll
LoadedModule[156]=C:\WINDOWS\SYSTEM32\clipc.dll
LoadedModule[157]=C:\Windows\System32\DevDispItemProvider.dll
LoadedModule[158]=C:\Windows\System32\NotificationControllerPS.dll
LoadedModule[159]=C:\Windows\System32\DDORes.dll
LoadedModule[160]=C:\Windows\System32\DefaultDeviceManager.dll
LoadedModule[161]=C:\Windows\System32\ActXPrxy.dll
LoadedModule[162]=C:\Windows\System32\EhStorShell.dll
LoadedModule[163]=C:\Windows\System32\Windows.UI.Xaml.dll
LoadedModule[164]=C:\WINDOWS\System32\cscui.dll
LoadedModule[165]=C:\WINDOWS\System32\wlidprov.dll
LoadedModule[166]=C:\Windows\System32\Windows.Networking.Connectivity.dll
LoadedModule[167]=C:\WINDOWS\system32\lockcontroller.dll
LoadedModule[168]=C:\Windows\System32\PCShellCommonProxyStub.dll
LoadedModule[169]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll
LoadedModule[170]=C:\Windows\ShellComponents\WindowsInternal.ComposableShell.DesktopHosting.dll
LoadedModule[171]=C:\WINDOWS\System32\UIAnimation.dll
LoadedModule[172]=C:\Windows\ShellComponents\WindowsInternal.ComposableShell.Experiences.Switcher.dll
LoadedModule[173]=C:\Windows\ShellExperiences\TileControl.dll
LoadedModule[174]=C:\Windows\ShellComponents\TaskFlowUI.dll
LoadedModule[175]=C:\Windows\ShellComponents\WindowsInternal.ShellUI.dll
LoadedModule[176]=C:\Windows\SystemApps\Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe\Microsoft.UI.Xaml.dll
LoadedModule[177]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe\VCRUNTIME140_1_APP.dll
LoadedModule[178]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe\VCRUNTIME140_APP.dll
LoadedModule[179]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe\MSVCP140_APP.dll
LoadedModule[180]=C:\Windows\System32\UiaManager.dll
LoadedModule[181]=C:\Windows\System32\WindowManagementAPI.dll
LoadedModule[182]=C:\WINDOWS\SYSTEM32\Windows.UI.Xaml.Controls.dll
LoadedModule[183]=C:\Windows\System32\Windows.Globalization.dll
LoadedModule[184]=C:\WINDOWS\SYSTEM32\daxexec.dll
LoadedModule[185]=C:\WINDOWS\System32\container.dll
LoadedModule[186]=C:\WINDOWS\SYSTEM32\cryptngc.dll
LoadedModule[187]=C:\WINDOWS\SYSTEM32\dmEnrollEngine.DLL
LoadedModule[188]=C:\WINDOWS\SYSTEM32\cflapi.dll
LoadedModule[189]=C:\Windows\System32\ShellCommonCommonProxyStub.dll
LoadedModule[190]=C:\Windows\System32\CloudExperienceHostRedirection.dll
LoadedModule[191]=C:\Windows\System32\wosc.dll
LoadedModule[192]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[193]=C:\WINDOWS\SYSTEM32\cryptsp.dll
LoadedModule[194]=C:\WINDOWS\SYSTEM32\rmclient.dll
LoadedModule[195]=C:\WINDOWS\System32\npmproxy.dll
LoadedModule[196]=C:\Windows\System32\IPHLPAPI.DLL
LoadedModule[197]=C:\WINDOWS\System32\NSI.dll
LoadedModule[198]=C:\Windows\System32\dusmapi.dll
LoadedModule[199]=C:\Windows\System32\CapabilityAccessManagerClient.dll
LoadedModule[200]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[201]=C:\Windows\System32\Geolocation.dll
LoadedModule[202]=C:\Windows\System32\BiWinrt.dll
LoadedModule[203]=C:\WINDOWS\system32\mssprxy.dll
LoadedModule[204]=C:\WINDOWS\SYSTEM32\MFPlat.DLL
LoadedModule[205]=C:\WINDOWS\SYSTEM32\RTWorkQ.DLL
LoadedModule[206]=C:\Windows\System32\SettingsHandlers_Backup.dll
LoadedModule[207]=C:\WINDOWS\system32\stobject.dll
LoadedModule[208]=C:\WINDOWS\system32\BatMeter.dll
LoadedModule[209]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[210]=C:\WINDOWS\System32\Windows.UI.Shell.dll
LoadedModule[211]=C:\WINDOWS\system32\WMICLNT.dll
LoadedModule[212]=C:\WINDOWS\system32\es.dll
LoadedModule[213]=C:\WINDOWS\system32\prnfldr.dll
LoadedModule[214]=C:\WINDOWS\SYSTEM32\windows.media.devices.dll
LoadedModule[215]=C:\WINDOWS\system32\dxp.dll
LoadedModule[216]=C:\WINDOWS\system32\SHDOCVW.dll
LoadedModule[217]=C:\WINDOWS\SYSTEM32\atlthunk.dll
LoadedModule[218]=C:\WINDOWS\System32\Actioncenter.dll
LoadedModule[219]=C:\WINDOWS\system32\Syncreg.dll
LoadedModule[220]=C:\Windows\System32\Windows.FileExplorer.Common.dll
LoadedModule[221]=C:\WINDOWS\system32\wpdshserviceobj.dll
LoadedModule[222]=C:\Windows\System32\PortableDeviceTypes.dll
LoadedModule[223]=C:\Windows\System32\PortableDeviceApi.dll
LoadedModule[224]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[225]=C:\WINDOWS\System32\cscobj.dll
LoadedModule[226]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[227]=C:\WINDOWS\System32\srchadmin.dll
LoadedModule[228]=C:\WINDOWS\System32\imagehlp.dll
LoadedModule[229]=C:\WINDOWS\SYSTEM32\windows.storage.search.dll
LoadedModule[230]=C:\WINDOWS\SYSTEM32\gpapi.dll
LoadedModule[231]=C:\WINDOWS\System32\SyncCenter.dll
LoadedModule[232]=C:\Windows\System32\SwitcherDataModel.dll
LoadedModule[233]=C:\Windows\System32\imapi2.dll
LoadedModule[234]=C:\Windows\System32\AudioSes.dll
LoadedModule[235]=C:\Windows\System32\CompPkgSup.DLL
LoadedModule[236]=C:\WINDOWS\System32\pnidui.dll
LoadedModule[237]=C:\WINDOWS\System32\netprofm.dll
LoadedModule[238]=C:\Windows\System32\NetworkUXBroker.dll
LoadedModule[239]=C:\Windows\System32\dhcpcsvc.DLL
LoadedModule[240]=C:\Windows\System32\dhcpcsvc6.DLL
LoadedModule[241]=C:\Windows\System32\msxml6.dll
LoadedModule[242]=C:\Windows\System32\EthernetMediaManager.dll
LoadedModule[243]=C:\Windows\System32\dot3api.dll
LoadedModule[244]=C:\Windows\System32\MobileNetworking.dll
LoadedModule[245]=C:\WINDOWS\System32\wlanapi.dll
LoadedModule[246]=C:\Windows\System32\bthprops.cpl
LoadedModule[247]=C:\WINDOWS\SYSTEM32\uiautomationcore.dll
LoadedModule[248]=C:\WINDOWS\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\ExplorerExtensions.dll
LoadedModule[249]=C:\WINDOWS\SYSTEM32\bluetoothapis.dll
LoadedModule[250]=C:\Windows\System32\deviceassociation.dll
LoadedModule[251]=C:\Windows\System32\InputSwitch.dll
LoadedModule[252]=C:\Windows\System32\NetworkIcon.dll
LoadedModule[253]=C:\Windows\System32\RasMediaManager.dll
LoadedModule[254]=C:\Windows\System32\rasman.dll
LoadedModule[255]=C:\Windows\System32\RASAPI32.dll
LoadedModule[256]=C:\Windows\System32\prxyqry.DLL
LoadedModule[257]=C:\Windows\System32\rtutils.dll
LoadedModule[258]=C:\Windows\System32\Windows.Energy.dll
LoadedModule[259]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[260]=C:\Windows\System32\DSROLE.dll
LoadedModule[261]=C:\Windows\System32\threadpoolwinrt.dll
LoadedModule[262]=C:\WINDOWS\system32\directmanipulation.dll
LoadedModule[263]=C:\Windows\System32\Windows.ApplicationModel.LockScreen.dll
LoadedModule[264]=C:\Windows\System32\WinLangdb.dll
LoadedModule[265]=C:\WINDOWS\System32\nlmproxy.dll
LoadedModule[266]=C:\WINDOWS\SYSTEM32\D3D10Warp.dll
LoadedModule[267]=C:\WINDOWS\SYSTEM32\pcacli.dll
LoadedModule[268]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[269]=C:\WINDOWS\System32\sfc_os.dll
LoadedModule[270]=C:\WINDOWS\SYSTEM32\ServicingCommon.dll
LoadedModule[271]=C:\Windows\System32\msi.dll
LoadedModule[272]=C:\Windows\System32\windows.internal.shell.broker.dll
LoadedModule[273]=C:\Windows\System32\icu.dll
LoadedModule[274]=C:\Windows\System32\UserDataTimeUtil.dll
LoadedModule[275]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.22000.318_none_ce876b9e12f802ea\gdiplus.dll
LoadedModule[276]=C:\WINDOWS\System32\wscinterop.dll
LoadedModule[277]=C:\WINDOWS\System32\WSCAPI.dll
LoadedModule[278]=C:\WINDOWS\System32\wscui.cpl
LoadedModule[279]=C:\WINDOWS\System32\werconcpl.dll
LoadedModule[280]=C:\WINDOWS\System32\framedynos.dll
LoadedModule[281]=C:\WINDOWS\System32\DiagnosticDataSettings.dll
LoadedModule[282]=C:\WINDOWS\System32\wer.dll
LoadedModule[283]=C:\WINDOWS\System32\hcproviders.dll
LoadedModule[284]=C:\WINDOWS\SYSTEM32\wevtapi.dll
LoadedModule[285]=C:\Windows\System32\IEProxy.dll
LoadedModule[286]=C:\Windows\System32\ieframe.dll
LoadedModule[287]=C:\Windows\System32\WINHTTP.dll
LoadedModule[288]=C:\WINDOWS\SYSTEM32\MLANG.dll
LoadedModule[289]=C:\WINDOWS\SYSTEM32\storageusage.dll
LoadedModule[290]=C:\WINDOWS\SYSTEM32\HID.DLL
LoadedModule[291]=C:\Windows\System32\DesktopSwitcherDataModel.dll
LoadedModule[292]=C:\Windows\System32\Windows.Graphics.dll
LoadedModule[293]=C:\WINDOWS\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\StartMenu.dll
LoadedModule[294]=C:\WINDOWS\system32\DUI70.dll
LoadedModule[295]=C:\WINDOWS\system32\DUser.dll
LoadedModule[296]=C:\Windows\System32\Windows.UI.FileExplorer.dll
LoadedModule[297]=C:\Windows\System32\AppContracts.dll
LoadedModule[298]=C:\Windows\System32\OnDemandBrokerClient.dll
LoadedModule[299]=C:\Windows\System32\Windows.Internal.Graphics.Display.DisplayEnhancementManagement.dll
LoadedModule[300]=C:\WINDOWS\SYSTEM32\winmmbase.dll
LoadedModule[301]=C:\WINDOWS\SYSTEM32\wdmaud.drv
LoadedModule[302]=C:\WINDOWS\SYSTEM32\ksuser.dll
LoadedModule[303]=C:\WINDOWS\SYSTEM32\AVRT.dll
LoadedModule[304]=C:\WINDOWS\SYSTEM32\msacm32.drv
LoadedModule[305]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[306]=C:\WINDOWS\SYSTEM32\midimap.dll
LoadedModule[307]=C:\Windows\System32\GameBarPresenceWriter.proxy.dll
LoadedModule[308]=C:\Windows\System32\Windows.Web.Http.dll
LoadedModule[309]=C:\WINDOWS\SYSTEM32\activationmanager.dll
LoadedModule[310]=C:\WINDOWS\SYSTEM32\profext.dll
LoadedModule[311]=C:\WINDOWS\SYSTEM32\capauthz.dll
LoadedModule[312]=C:\Windows\System32\dlnashext.dll
LoadedModule[313]=C:\Windows\System32\WorkFoldersShell.dll
LoadedModule[314]=C:\WINDOWS\system32\IconCodecService.dll
LoadedModule[315]=C:\WINDOWS\SYSTEM32\samcli.dll
LoadedModule[316]=C:\WINDOWS\SYSTEM32\rometadata.dll
LoadedModule[317]=C:\WINDOWS\SYSTEM32\licensemanagerapi.dll
LoadedModule[318]=C:\WINDOWS\System32\p9np.dll
LoadedModule[319]=C:\WINDOWS\System32\drprov.dll
LoadedModule[320]=C:\WINDOWS\System32\ntlanman.dll
LoadedModule[321]=C:\WINDOWS\System32\davclnt.dll
LoadedModule[322]=C:\Windows\System32\cdprt.dll
LoadedModule[323]=C:\WINDOWS\system32\execmodelproxy.dll
LoadedModule[324]=C:\Windows\System32\Windows.StateRepositoryBroker.dll
LoadedModule[325]=C:\Windows\System32\lxss\wslsupport.dll
LoadedModule[326]=C:\Program Files\PowerToys\modules\PowerRename\PowerRenameExt.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=22000
OsInfo[3].Key=ubr
OsInfo[3].Value=376
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=118
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=221405903
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.1.22000.0-11.0.1000
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16318
OsInfo[19].Key=svolsz
OsInfo[19].Value=231
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=210604
OsInfo[22].Key=bldtm
OsInfo[22].Value=1628
OsInfo[23].Key=bldbrch
OsInfo[23].Value=co_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.22000.376.amd64fre.co_release.210604-1628
OsInfo[30].Key=buildflightid
OsInfo[30].Value=fc24e3f1-eb03-4055-852c-c2bf74820a48
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=FX:117B97D4,FX:117B9872,FX:11CC111C,FX:11DF5B12,FX:11DF5B75,FX:11EF28AE,FX:11EFAF3E,FX:12085A48
OsInfo[34].Key=fconid
OsInfo[34].Value=18299130,0,2,1;19638787,0,2,1;23531064,2,2,1;23562335,2,2,1;23563673,2,2,1;24172318,0,1,1;25704915,1,2,1;27368843,0,2,1;27371152,6,2,1;35409375,0,2,0
OsInfo[35].Key=containerid
OsInfo[36].Key=containertype
OsInfo[37].Key=edu
OsInfo[37].Value=0
OsInfo[38].Key=servicinginprogress
OsInfo[38].Value=0
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Windows Explorer
AppPath=C:\Windows\explorer.exe
ReportDescription=A problem caused this program to stop interacting with Windows.
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=8E925A23694981BE88D2EFC7EFABE2AA
MetadataHash=-1766035028

And this is the Registry

DanPinGF commented 2 years ago

@OneBlue - Be careful; if the author doesn't provide any further info after a while, this issue is likely to be tagged again with 'needs-author-feedback'.

OneBlue commented 2 years ago

Thanks @alex180500. The registry key looks normal.

Can you please collect logs via feedback hub ? If the explorer crashes during the repro I should be able to see that

alexander-paterson commented 2 years ago

I don't know about the other people in here this affects but for me it is going to be a bit hard to capture with the recording in the feedback hub. It isn't like I'm actively browsing the WSL file system in explorer and it starts to hang, I can access it fine then I can go back 30/60/90 minutes later and it has hung.

alex180500 commented 2 years ago

Having an hard time trying to repro the bug in these days, I don't have a consistent way, if anybody else manages to collect the log via the feedback reproduction it would be awesome. (PS Merry Christmas everybody)

marco-pm commented 2 years ago

Log attached. Although I don't know if it will be useful, for the reason stated by @alexander-paterson. wsl.zip

OneBlue commented 2 years ago

Thanks @marco-pm, unfortunately I don't see anything in the logs that would explain this issue.

Besides the Feedback hub logs, the 9p verbose logs would be really useful here. Quoting @Biswa96, the way to enable the logs is to add:

[fileServer]
logFile=/9p-logs.txt

to /etc/wsl.conf (let's not use /mnt/c since something is clearly wrong with 9p).

Then share the resulting 9p-logs.txt after a repro.

marco-pm commented 2 years ago

Thanks @marco-pm, unfortunately I don't see anything in the logs that would explain this issue.

Besides the Feedback hub logs, the 9p verbose logs would be really useful here. Quoting @Biswa96, the way to enable the logs is to add:
[fileServer]
logFile=/9p-logs.txt
to /etc/wsl.conf (let's not use /mnt/c since something is clearly wrong with 9p).

Then share the resulting 9p-logs.txt after a repro.

Done. At first (for several hours, while I was using File Explorer normally) only a series of these three connection entries:

INFO:     PostAccept
INFO:     Accepted connection.
INFO:     Connection disconnected.

After the issue arose, the logging simply stopped. No errors, no more entries. After a shutdown and restart of WSL2, Server started. is logged, but after that still no more entries.

OneBlue commented 2 years ago

Thanks @marco-pm. Can you share both the 9p logs and the rest of the wsl logs from the same repro ?

swichers commented 2 years ago

This may be weirdly related to the 500 series NVIDIA driver. I was having this issue (and various other ones that stem from it) consistently and daily. I recently downgraded to 472.12 and cannot duplicate the problem any longer. Worth checking if you have an NVIDIA card.

alex180500 commented 2 years ago

I don't think the problem is GPU related, I've got an AMD card (RX 580). Maybe you have problem replicating it because this bug is really unpredictable, I also have difficulties replicating this bug consistently.

marco-pm commented 2 years ago

Thanks @marco-pm. Can you share both the 9p logs and the rest of the wsl logs from the same repro ?

Like others, I'm struggling a bit to reproduce the bug and collect the logs. It has almost never happened in the last few days, which I strange because practically nothing has changed in my system (no system/drivers/store updates, no changes to installed apps, etc.). Collecting the logs with wpr is a bit of a hassle because if left running over time it generates a bigger and bigger (like 2 GB) trace file, so until the bug shows up I have to stop it and restart it manually every 1-2 hours or so (to avoid having a huge trace file). And again, it appears that this log and the 9p logs are not very helpful in identifying the cause of the problem.

benhillis commented 2 years ago

Thanks everybody for your help so far, I'm actively working on getting a local repro.

ByteProject commented 2 years ago

Thanks @benhillis, I have the same problem here. And it is not only the file explorer. It's generally if you're trying to execute an Windows binary from WSL. Could be Explorer.exe could be Notepad.exe, it really doesn't matter. It keeps crashing and only a reboot is capable of getting back to normal. The only thing that really helped is uninstalling the Store version. This issue is definitely somehow connected to the Store version as the issues began after I installed it and completely went away after I uninstalled the store version.

jsquire commented 2 years ago

Since reverting to the bundled Windows feature version, I've noticed that the hang behavior does not present, but accessing the WSL filesystem from Windows does seem to degrade over time. This was also an issue in the Windows Store version, but I had assumed it was related to the hang.

In my scenario, I've got source code in the WSL file system that I'm editing with Visual Studio. When I first start working in a directory, running and debugging takes place with the same general performance as doing so for items in the Windows filesystem. Over time, it takes several (~5-10) minutes for Visual Studio to fully launch the test host and attach the debugger. If I nuke the directory, recreate, and clone the repository, performance is normal for a bit and then degrades again.

To be fair, I cannot rule out Visual Studio 2022 and/or Windows 11 as the culprit here; I did not have these issues with the same scenario using Win10 / VS2019 / and the bundled WSL - they started after a clean format + rebuild with Win11. To date, I have not yet gotten around to reinstalling VS2019 to see if the experience is equivalent.

marco-pm commented 2 years ago

I don't know if this may help identify the cause and if others are experiencing the same: when the problem occurs, not only the WSL filesystem becomes inaccessible from File Explorer, but also:

directories (any Windows path, including desktop) no longer refresh automatically to reflect file changes; I have to refresh them manually
when using an "Open File" dialog in any application, after selecting the file, the loading of the file afterwards freezes for about 3-4 seconds

microsoft / WSL