microsoft
Long issue P9 file explorer (provider oder) - reset after reboot
Windows Version
Microsoft 10.0.22631.3880
WSL Version
All of them
Are you using WSL 1 or WSL 2?
- [x] WSL 2
- [ ] WSL 1
Kernel Version
5.15.167.4
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
This has been reported multiple times: https://github.com/microsoft/WSL/issues/4027 but it was closed.
To summarize it:
- Provider Order misses P9NP in the list.
- Modifying the registry and adding P9NP as the first in the ProviderOrder fixes the issue of not being able to access \wsl$ through file explorer.
- However, each time the laptop is rebooted, the issue came up again because it's wiped out.
Expected Behavior
- P9NP Provider sticks after establishing it, so it's not required to do it each time after reboot. Quite annoying.
Actual Behavior
- P9NP gets removed from registry each time after reboot.
Diagnostic Logs
No response
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1
The script will output the path of the log file once done.
If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here
Once completed please upload the output files to this Github issue.
Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1
The script will output the path of the log file once done.
If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here
Once completed please upload the output files to this Github issue.
Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
Diagnostic information
Found '/question', adding tag 'question'
For me, i got the same problem after restart ( try to fix broken \wsl.localhost button on left-size bar ). Box driver value "cbfsconnect2017" was the thing that stood before P9NP Provider in the list and broke \wsl.localhost button on left-size bar. But when i uninstall Box driver then reinstall it, even if i restart the computer \wsl.localhost button worked fine and the order of those value still the same. ( i haven't try to change value in ProviderOrder )
