fkelava
commented
3 years ago Here's the relevant log, this time for a Notepad++ install.
WinGet-2021-09-05-17-27-33.910.log
Note the relevant segment:
2021-09-05 17:27:36.490 [FAIL] E:\BA\98\s\external\pkg\src\AppInstallerCLICore\Workflows\ShellExecuteInstallerHandler.cpp(269)\AppInstallerCLI.exe!00007FF7B59D2F01: (caller: 00007FF7B58520B0) LogHr(1) tid(22c8) 8007023E {Application Error}
The exception %s (0x Msg:[std::exception: rename: The system cannot find the file specified.: "C:\Users\FRAN~1.KEL\AppData\Local\Temp\WinGet\Notepad++.Notepad++.8.1.4", "C:\Users\FRAN~1.KEL\AppData\Local\Temp\WinGet\Notepad++.Notepad++.8.1.4.exe"]
2021-09-05 17:27:36.745 [CLI ] Caught std::exception: rename: The system cannot find the file specified.: "C:\Users\FRAN~1.KEL\AppData\Local\Temp\WinGet\Notepad++.Notepad++.8.1.4", "C:\Users\FRAN~1.KEL\AppData\Local\Temp\WinGet\Notepad++.Notepad++.8.1.4.exe"This makes no sense, as
PS C:\Users\fran.kelava> ren 'C:\Users\fran.kelava\AppData\Local\Temp\WinGet\Notepad++.Notepad++.8.1.4' 'C:\Users\fran.kelava\AppData\Local\Temp\WinGet\Notepad++.Notepad++.8.1.4.exe'and
PS C:\Users\fran.kelava> ren 'C:\Users\FRAN~1.KEL\AppData\Local\Temp\WinGet\Notepad++.Notepad++.8.1.4' 'C:\Users\FRAN~1.KEL\AppData\Local\Temp\WinGet\Notepad++.Notepad++.8.1.4.exe'can be performed successfully.
oleksis
jedieaston
Masamune3210
xezrunner
vedantmgoyal9
ghost
naveenkrdy
shivangswain
ItzLevvie
Brief description of your issue
winget installfails to expand paths when encountering user profiles with a name longer than 8 characters. Specifically, a call tostd::filesystem::renamewill fail. A trigger may also be a space or dot, or any other special character in the user profile path.A notable example of the latter are accounts provisioned from Azure AD, as these commonly take the form of
NameSurname, not normalizing special characters, e.g.IvoIvić, orname.surname, e.g.fran.kelava.Steps to reproduce
This is perfectly reproducible using any package. You do not need to use the exact package from the example.
During your Windows install, sign in with an MSA/AAD account. Your resulting user directory name may include special characters or a dot separating your name and surname, and this must be the case to trigger this issue. OR During your Windows install, skip MSA/AAD login and create a local account longer than 8 characters in length, and add a space in it for good measure.
Expected behavior
The command throws no error.
Actual behavior
This may also be related to the problem showcased in #1203, in which an AAD-based account suffered a similar or identical issue. While the author of that issue also had special characters making the issue more difficult, the issue also plainly appears for usernames which do not feature special characters.
In #1203, the issue author saw functionality restored once the dot and special characters were eliminated from the user directory name. [UPDATE] However, based on the replies below, it seems that this is an issue with path expansion in general.
However, I'm afraid I must insist that this issue be properly fixed. It is not acceptable for
wingetto ship broken by default in instances where the user cannot influence the name of their user directory, e.g. Azure AD joins in OOBE.Environment