Receiving Console Errors deploying a Sysprepped Win 7 Image
I'm attempting to deploy a sysprepped Windows 7 image from the K2000. I'm getting errors on files present in the winsxs folder after deploying the image to a client machine. The console says "Error in SetFileShortName" . There are about a dozen of these listed. Does anyone know how to fix this?
0 Comments
[ + ] Show comments
Answers (1)
Answer Summary:
There is nothing to fix, this is just telling you that when we lay the system backdown, there was an error setting the shortname of that file, because it was already taken by another file. Windows will reassign the file a new shortname. For example: To be backwards compatible back to FAT (and DOS), NTFS has two names for each file. The end user typically only interacts with the long name, but the short 8.3 name is there behind the scenes. Unless 8.3 creation has been disabled by a registry change, when you create a file, the 8.3 name is automatically generated for you. The names typically will have a particular pattern: 1. ABCDEFGHIJKL.TXT -> ABCDEF~1.TXT 2. ABCDEFGHIJKLM.TXT -> ABCDEF~2.TXT 3. And so on. But, if you create them in a different order, the numbers will change: 1. ABCDEFGHIJKLM.TXT -> ABCDEF~1.TXT 2. ABCDEFGHIJKL.TXT -> ABCDEF~2.TXT
There is nothing to fix, this is just telling you that when we lay the system backdown, there was an error setting the shortname of that file, because it was already taken by another file. Windows will reassign the file a new shortname. For example: To be backwards compatible back to FAT (and DOS), NTFS has two names for each file. The end user typically only interacts with the long name, but the short 8.3 name is there behind the scenes. Unless 8.3 creation has been disabled by a registry change, when you create a file, the 8.3 name is automatically generated for you. The names typically will have a particular pattern: 1. ABCDEFGHIJKL.TXT -> ABCDEF~1.TXT 2. ABCDEFGHIJKLM.TXT -> ABCDEF~2.TXT 3. And so on. But, if you create them in a different order, the numbers will change: 1. ABCDEFGHIJKLM.TXT -> ABCDEF~1.TXT 2. ABCDEFGHIJKL.TXT -> ABCDEF~2.TXT
Please log in to answer
Posted by:
cserrins
12 years ago
There is nothing to fix, this is just telling you that when we lay the system backdown, there was an error setting the shortname of that file, because it was already taken by another file. Windows will reassign the file a new shortname.
For example:
To be backwards compatible back to FAT (and DOS), NTFS has two names for each file. The end user typically only interacts with the long name, but the short 8.3 name is there behind the scenes. Unless 8.3 creation has been disabled by a registry change, when you create a file, the 8.3 name is automatically generated for you.
The names typically will have a particular pattern:
1. ABCDEFGHIJKL.TXT -> ABCDEF~1.TXT
2. ABCDEFGHIJKLM.TXT -> ABCDEF~2.TXT
3. And so on.
But, if you create them in a different order, the numbers will change:
1. ABCDEFGHIJKLM.TXT -> ABCDEF~1.TXT
2. ABCDEFGHIJKL.TXT -> ABCDEF~2.TXT
For example:
To be backwards compatible back to FAT (and DOS), NTFS has two names for each file. The end user typically only interacts with the long name, but the short 8.3 name is there behind the scenes. Unless 8.3 creation has been disabled by a registry change, when you create a file, the 8.3 name is automatically generated for you.
The names typically will have a particular pattern:
1. ABCDEFGHIJKL.TXT -> ABCDEF~1.TXT
2. ABCDEFGHIJKLM.TXT -> ABCDEF~2.TXT
3. And so on.
But, if you create them in a different order, the numbers will change:
1. ABCDEFGHIJKLM.TXT -> ABCDEF~1.TXT
2. ABCDEFGHIJKL.TXT -> ABCDEF~2.TXT
Comments:
-
Thank you for the explanation! - CUdeploy 12 years ago
