JFX
-
Posts
1,230 -
Joined
-
Days Won
6 -
Donations
0.00 USD
Content Type
Profiles
Forums
Events
Posts posted by JFX
-
-
Yes, I file backed copy is slow. Sadly wimlib only uses 1 thread to do the apply stuff.
Volume copy mode, runs on the max speed of your hardware, but if the destination drive is smaller
there is no guarantee that it will work. the last cluster have to fit into the new partition.Even the shrink option may not be able to move some system files.
0 -
Maybe you use Windows 7 or some other old OS, here?
By default WinCopy uses a wimlib capture and apply, but without actually creating a WIM file.
So yes, WimScript.ini is needed and if not set by command line, that the default one is used.Not sure what problem wimlib has, that error codes could be during scan and apply.
I uploaded a "b" version that will add wimlib error file to the console output.Anyway you could also try volume mode of WinCopy by adding "-volume" to the command line.
1 -
WinNTSetup_x64.exe wincopy-cli S: T:S: - source drive
T: - target drive0 -
Yeah, Disk2VHD is properly only thought to copy entire disk and boot it in a VM.
Also be careful with creating a VHD entry with bootice, that's not fully supported, better mount and use bcdboot for it.
WinNTSetup's Wincopy should do what you want.
0 -
Uploaded a fix version, the RunAsTI ini option should not be needed anymore.
2 -
Would call that a lazy question, took just 5 minutes to try and verify that it boots normally.
1 -
There is nothing to worry about.
WinNTSetup just check if the target partition has the set FILE_ATTRIBUTE_NOT_CONTENT_INDEXED.
That is what the last checkbox of drive properties (if unchecked) means.Only in that case, WinNTSetup will inherit FILE_ATTRIBUTE_NOT_CONTENT_INDEXED to all files and folder,
that will be applied from the wim/esd file.
0 -
The RunAsTI problem will be fixed.
Are you sure the second problem isn't caused by this NTLite source?
Please post the log file H:\Windows\Logs\WinNTSetup\*\WinNTSetup.logAnd what happens if you manually run bcdboot.exe?
bcdboot H:\Windows /s H: /f BIOS
0 -
Good, I will add a fallback for RunAsTI setting.
About the crash, is there anything in windows eventlog?
0 -
21 hours ago, sharicov@gmail.com said:
winntsetup 5.3.3 crashed with windows 2022 datacenter desktop installation to new vhd
vhd was created, but winntsetup window closed when ran setup.
Is a crashdump created or can you post the error information from event log?
21 hours ago, sharicov@gmail.com said:version 5.3.1 working well for same task with same environment (ran under up to date windows 10 x64)
Error window says "Applying System image failed!"
Newer version will execute "Tools\x64\WIMHost.exe" to apply the WIM file.
If no error code is displayed, it could only mean that the program did not even start.Maybe an antivirus program intercept here or WinNTSetup is located on a network share.
WinNTSetup tries to run WIMHost.exe with "trusted installer" rights maybe that is the problem.
Add a WinNTSetup.ini next to WinNTSetup_x64.exe with following contain, and try again.
[WimHost] RunAsTI=00 -
Hmm, just don't delete the files it comes with.
Unless there are critical bugs or needed changes for Windows 12, no further development is planed.0 -
Last version could fallback to xpress compression and also ignoring the compression level.
I don't think "merge ide" will cause any problems, but i would not recommend to use it without reason.
I is really only thought to apply or copy a not generalized image to different hardware.
1 -
WinNTSetup 5.3.3
- fixed wim capture regressions
- fixed trusted installer could not access temporary drive letters
- automatically switch to wimlib, for non solid ESD (fix wimgapi crash)
- wincopy commandline volume mode can use filemode as fallback
- vhd drives can be saved and loaded from ini file0 -
With slim taskbar the systray icons are no longer centered.
TaskBand2SmallIcons::Taskband2, TASKITEM --> CONTENTMARGINS = 4,4,4,4
1 -
MergeIDE tweak can be useful, if you capture a fully installed Windows and apply it on different hardware.
With older OS you could often get a 0x7B BSOD caused by different SATA drivers.I don't know if it makes much sense with Win8 and later.
2 -
WinNTSetup.ini.txt only show the hidden options. Most of them are uses in initialization and can't be changed later while loading a new ini file.
if you want to document the normal GUI options, sure do and I will add it.0 -
WinNTSetup 5.3.2
- native ARM64 code for WIM apply and capture
- WIM apply and capture will be executed as "trusted installer"
- WIM capture UI adds compression level, defaults to wimlib's LZX Fast
- wimlib wimboot apply - changed overlay type to WIM_BOOT_OS_WIM
- wimlib capture WIM - deletes incomplete WIM after operation cancel
- wimlib smooth progress bar for appending operation
- using customized wimlib.dll (do not update!)
- automatically switch to wimlib, if wimgapi can not load WIM file
- fixed cancel setup was ignored during DISM operations
- fixed WinCopy Volume mode problems
- fixed some issues with ARM64 sources
- added advanced VHD creation options
- respect NTFS indexing option on target partition
- no longer downloads ADK files on Win10/11 Host3 -
A warning, yes that should be added.
But more options will not be added. It's just a simple action like get used clusters and copy them.
Adding exclusions would require complete MFT parsing, what I don't have the time to implement.2 -
Mount the VHD and than create backups like you do on every other normal disk system.
Either a disk imaging software like Acronis TI, Macrium Reflect or a file backing image like a WIM backup.
2 -
Yes, it working for me, using it from time to time. But the grow rate is quite high.
Just booted a diff and shutdown after 3 minutes it grow to 1.42 GB.You could simplify this without editing BCD.
Just rename the VHD to let's say Base.vhd and create a diff with the old name.Also make sure that parent and diff vhd are in the some folder.
1 -
Maybe, differencing VHDs are not the best choice for you
Have not seen that 0xC0000000f error. Could be a problem coming from Bootice edit.
0 -
No, but {default} is the correct one.
"bcdedit -v -store Q:\Boot\BCD" would show the correct GUID, but you can use symbols like {default} or {current}, too.
0 -
"bcdedit -store Q:\Boot\BCD" should print something like this:
QuoteWindows-Startladeprogramm
-------------------------
Bezeichner {1445ab79-433b-4e96-82ee-3b86552f7a64}
device vhd=[E:]\Win10H2.vhd
path \Windows\system32\winload.efi
description Windows 10 (VHD)
0 -
Yes, that would require to do all steps manually.
Update BCD with bcdedit.exe:
Get the %GUID% form
bcdedit -store S:\EFI\Microsoft\Boot\BCDthan update device and osdevice:
bcdedit -store S:\EFI\Microsoft\Boot\BCD -set %GUID% device vhd=[C:]\diff.vhd bcdedit -store S:\EFI\Microsoft\Boot\BCD -set %GUID% osdevice vhd=[C:]\diff.vhd1
WinNTSetup v5.3.4
in Install Windows from USB
Posted
You can use bootice to set BootMenuPolicy to legacy for every boot option.
But make sure you also disable fastboot for every system,
cause this is there reason for these additional reboots (making a clean shutdown).