No short name when wimapplying on winPE?
Library to create, extract, and modify Windows Imaging (WIM) files
Brought to you by:
synchronicity
Menu
▾
▴
First of all, I want to thank you for this marvelous tool.
I love this opensource alternative to wimglib/dism which can apply WIMboot without any modification.
However, it seems to have a small problem, that short file names (DOS, 8.3 filenames) haven't been extracted when I try to wim-apply on Windows PE. (at least in Windows Setup stage)
I checked they are extracted properly on installed Windows.
(tested with wimapply -wimlib-imagex apply- only, maybe library itself can handle it properly with some trick)
I know shortname doesn't matter in most case using modern Windows system, so I'll keep using this great tool, but still wish to have it for fallback[?]
Thanks again Mr. Bigger, and sorry for my bad English skill.
ps. I don't know if there's any way to enable logging or shortname-related messages, so please provide me such thing when replying.
Are you using wimlib v1.7.2-BETA? I recently added two "bug-fixes" (or rather, workarounds for bugs in Windows) related to setting short names on Windows. They are present in v1.7.2-BETA, so please try it if you haven't already.
I didn't try applying with testing version but only 1.7.1.
I just reinstalled Windows in WIMboot with 1.7.2-BETA and it does work setting short names with it... Sorry for bothering
Hi synchronicity,
I tested wimlib 1.72 to image and restore a Windows 10 Technical Preview installation. The backup process finished successfully. However, if the .wim file is in the system partition, wimlib will complain about shortnames :
C:\Win10TechPrev.wim applied to C:\
D:\wimlib172>wimlib-imagex.exe apply C:\Win10TechPrev.wim 1 C:\ Applying image 1 ("C:") from "C:\Win10TechPrev.wim" to directory "C:\"
Creating files: 80998 of 80998 (100%) done
Extracting files: 5505 MiB of 5505 MiB (100%) done
Applying metadata to files: 80998 of 80998 (100%) done
[WARNING] Extraction to "C:\" complete, but with one or more warnings:
[WARNING] - Could not set short names on 1921 files or directories
Done applying WIM image.
If I copy the .wim file to another location then wimlib restores the operating system without any issues :
R:\Win10TechPrev.wim applied to C:\
D:\wimlib172>wimlib-imagex.exe apply R:\Win10TechPrev.wim 1 C:\ Applying image 1 ("C:") from "R:\Win10TechPrev.wim" to directory "C:\"
Creating files: 80998 of 80998 (100%) done
Extracting files: 5505 MiB of 5505 MiB (100%) done
Applying metadata to files: 80998 of 80998 (100%) done
Done applying WIM image.
wimlib is operating in a Windows PE environment.
Last edit: Vortex 2014-10-09
Hi,
It makes no sense for the behavior to be different depending on where the WIM file is. Probably there's another factor involved (e.g. are you starting with a clean C:\ each time?).
Which version of Windows PE are you using?
Also: in the 'testing' directory I posted wimlib-imagex builds that support a new '--strict-short-names' option to 'wimlib-imagex apply'. Try reproducing this problem when using the '--strict-short-names' option and post any error message received.
Hi synchronicity,
The C:\ drive is clean and it contains only the .wim file Win10TechPrev.wim.
The short name error appears if I restore the .wim archive on a WinPE 1.x ( based on Windows XP ) system.
Switching to a Win7PESE system, I don't receive the short name error message. Again, the OS is restored from C:\Win10TechPrev.wim
Thanks for the test release. Booting off of a WinPE 1.x disc, I tested wimlib-imagex_testing_i686.exe Trying to restore the OS from C:\Win10TechPrev.wim :
wimlib-imagex_testing_i686.exe apply C:\Win10TechPrev.wim 1 C:\ --strict-short-names
Applying image 1 ("C:") from "C:\Win10TechPrev.wim" to directory "C:\"
[ERROR] Can't set short name on "C:\PerfLogs" (status=0xc000000d)
ERROR: Exiting with error code 60:
Failed to set short name on extracted file.
Hi,
The problem is that versions of Windows prior to Windows 7 do not allow removing short names from files. Some files in the WIM image must not have short names specified, so wimlib needs to remove the Windows-generated short names from them to correctly extract them. However, this is not supported by the version of Windows you are running.
It's impossible for me to fix this in the general case. And the only difference between wimlib 1.7.2 and earlier versions in this regard is the warning messages I happened to add around short name restore failures.
So if you have to use a Windows XP based operating system I suggest you just ignore the warnings and hope you don't experience any problems. Probably you won't, though. Funnily enough, Microsoft's WIMGAPI has a bug where it sets incorrect short names on some files, tested running on Windows8.1u1, and people seem to get by with that...
Hi synchronicity,
Thanks for the information. The practical solution is to use a Windows 7 based PE disc. I didn't have any problems after ignoring the warnings.
Dear synchronicity,
Firstly, thank you very much for this excellent tool. Especially it's wonderful able to running under NT5.
I writing about the same issue. I tried WimLib 1.7.2 in a Windows XP PE (Hiren's Boot 15.2 mini xp). That used As WIM Image (ESD): Windows 8.1 Update
WimLib is displayed the same warning messages after finished extracting:
After, I did boot settings (bcdboot, bootsect). The system can't boot.
Again formatted C. This time, I tried WimLib 1.7.1. No Warning messages, no problem. After boot settings, Windows 8 booted without problem.
Lastly, Wimlib 1.7.1 is last version that whole compatible with WinXP PE.I'm sorry, my bad English.
Best regards...
Last edit: oceanpure 2014-10-26
Hi,
I find it hard to believe that the alleged problems with short filenames would
render a modern version of Windows completely unbootable. In addition, the
effect of the limitations of Windows XP on wimlib should be the same on both
wimlib 1.7.1 and wimlib 1.7.2, even if wimlib 1.7.2 is more noisy about the
errors that Windows is returning.
If you are able to tell me why Windows isn't booting, that would be very
helpful in tracking down the cause of the problem. (But if you can't, no
worries; Microsoft makes it nearly impossible to track down failures in their
operating system's boot process anyway.)
I did, however, decided to see if there is anything I can do about versions of
Windows prior to 7 not supporting removing short names from files. It seems
extraordinarily unlikely that the mere fact that a file that has a short name
when it should not could cause problems. What can happen, however, is that a
short name assigned to one file can prevent that short name from being assigned
to another file. So my workaround is to remove, or replace with random
characters if that does not work, an existing short name that conflicts with one
that needs to be explicitly set.
You're welcome to try wimlib v1.7.3-BETA to see if this solves your problem, but
do keep in mind that if it does, it only proves that my fix actually had an
effect if your test was completely controlled.
And of course, I suggest you use wimlib on Windows 7 or later, or on Linux using
the ntfs-3g support, to avoid any limitations of Windows XP.
Hello synchronicity,
Firstly, thank you very much for your interest and detailed reply.
And I'm sorry;
a) for replying late.
b) for my false feedback. Because of the issue not related about short filenames. You're right. In fact, my boot problem is wrong order running of boot commands. I've ran bootsect after bcdboot. :) Of course, Bootsect.exe should've run as first.
True sequences: http://i.imgur.com/LpLsjMS.jpg
synchronicity, I apologize again for my mistake. And I thank you for giving me informations.
Sincerely...
No worries, I always appreciate receiving feedback. Even if it turns out to be wrong, it often motivates me to make other improvements, as happened in this case.