P
PeterSchubel
Since updating to Win10 build 1803, I have problems building projects with Visual Studio 2013. The linker fails when generating the manifest, probably due to incorrect white-space handling of paths.
The error message in Visual Studio is e.g.: "C:\Users\Peter : general error c1010070: Failed to load and parse the manifest. Windows was unable to parse the requested XML data.". The first part "C:\Users\Peter " strongly suggests that the issue is due to something in the build chain or the OS not respecting white-space in the user name. Note, my local username is "Peter Schuebel".
This issue was first reported by alschmitt (using Visual Studio 2017) at the developer support site, see: general error c1010070: Failed to load and parse the manifest. Windows was unable to parse the requested XML data. - Developer Community. But they replied that it is a Windows issue: "We have determined that this issue belongs to Windows team. please move this feedback ticket to the right team."
I tried contacting Windows support at https://support.microsoft.com/en-gb/contactus/ with the message below, but got no reply or even confirmation.
Workaround:
As mentioned, this definitely is connected to the whitespace in the user name directory. I'm signing into my machine with a Microsoft account, which automatically created a username with a whitespace between first and last name. Changing my current user's sign-in option to a local account without whitespace did not help, since the existing user folder remains unchanged in that case.
But creating a new local user (without whitespace in the user name) seems to work. After signing in with the new local user, carrying across some settings, changing permissions, etc, the Visual Studio build worked fine again.
It's not great, since I now end up switching between two users, but it is a workaround for the short term.
Can this please get looked at by the Windows dev team and get fixed? If I'm posting this in the wrong place, then please please make it clearer where to report bugs like this.
Thank you very much,
Peter
[Windows user since 1992, version 3.1]
Continue reading...
The error message in Visual Studio is e.g.: "C:\Users\Peter : general error c1010070: Failed to load and parse the manifest. Windows was unable to parse the requested XML data.". The first part "C:\Users\Peter " strongly suggests that the issue is due to something in the build chain or the OS not respecting white-space in the user name. Note, my local username is "Peter Schuebel".
This issue was first reported by alschmitt (using Visual Studio 2017) at the developer support site, see: general error c1010070: Failed to load and parse the manifest. Windows was unable to parse the requested XML data. - Developer Community. But they replied that it is a Windows issue: "We have determined that this issue belongs to Windows team. please move this feedback ticket to the right team."
I tried contacting Windows support at https://support.microsoft.com/en-gb/contactus/ with the message below, but got no reply or even confirmation.
Workaround:
As mentioned, this definitely is connected to the whitespace in the user name directory. I'm signing into my machine with a Microsoft account, which automatically created a username with a whitespace between first and last name. Changing my current user's sign-in option to a local account without whitespace did not help, since the existing user folder remains unchanged in that case.
But creating a new local user (without whitespace in the user name) seems to work. After signing in with the new local user, carrying across some settings, changing permissions, etc, the Visual Studio build worked fine again.
It's not great, since I now end up switching between two users, but it is a workaround for the short term.
Can this please get looked at by the Windows dev team and get fixed? If I'm posting this in the wrong place, then please please make it clearer where to report bugs like this.
Thank you very much,
Peter
[Windows user since 1992, version 3.1]
Continue reading...