microsoft
WinGet Log file is locked when Dev Home is open
Dev Home version
1.0.0.0
Windows build number
10.0.22621.1635
Other software
OS Build Version: 10.0.22621.1635.amd64fre.ni_release.220506-1250 .NET Version: .NET 6.0.16
Steps to reproduce the bug
Launch Dev Home. Navigate to the WinGet logs folder. Open the "WinGetCOM…" log file that is associated with Dev Home. Receive error that file is locked.
Expected result
Log files open and show information
Actual result
Error: File is locked.
Included System Information
CPU: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz Physical Memory: 15.92GB (2.54GB free) Processor Architecture: x64
This sounds expected to me, depending on the editor you were trying to open the logs with. Notepad seems to be bad for opening files that other processes have open; and it will fail to open the current winget log file regardless of who is calling it (winget or Dev Home). VSCode seems to be able to open the log file just fine. So this doesn't sound like an issue on Dev Home to me
