October 26, 20232 yr Antonino, I uncheck the indexing box in an empty VHD; after deployment it used to be enabled, but now it’s not, which is what I need.
October 27, 20232 yr thanks a lot., this is what I need too, so how do I get it now that it is no longer automatic? can we re-automate it or automate it in any other way?
October 27, 20232 yr Author 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.
October 27, 20232 yr i can confirm jfx is correct!!! so we'll have to take good care to have the box unchecked beforehand if we want no indexing, btw, I have a feeling that only my old captured wims work properly; I have never succeeded to make a dvd out of what I have just recaptured. I do not know what the resason might be; it never was so with any previous version. there must be something wrong with my capturing (and recapturing, for that matter). whoops, sorry - I tried once again and ... no issue this time. so I guess it all depended on my postmodified vhds Edited October 27, 20232 yr by Antonino
October 28, 20232 yr probably a stupid question, but I wll ask it anyway: can an already minwinned vhd be minwinned again and reboot ok?
October 30, 20232 yr Author Would call that a lazy question, took just 5 minutes to try and verify that it boots normally.
October 30, 20232 yr Author Uploaded a fix version, the RunAsTI ini option should not be needed anymore.
November 4, 20232 yr What's the best way to add an additional vhdx to a partition that already has another bootable vhdx? I created a vhdx with disk2vhd from sysinternals and added it to the current BCD used to boot my other vhd with Bootice. I get the Bootmgr Menu that shows both vhd entries, but only the original vhd will boot. The new one doesn't and returns with a blue screen cannot Start message. I have a feeling Disk2VHD doesn't create a vhd that can be used for what I want to do. I only need a vhd of the partition and not the entire disk. I'll try the Copy windows Installation. Edited November 5, 20232 yr by click-click
November 5, 20232 yr Author 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.
November 7, 20232 yr What would the command line syntax for WINCOPY or WINCOPY-CLI be, to copy the partition to the mounted vhd? I keep getting the normal WInNTSetup GUI. Edited November 7, 20232 yr by click-click
November 7, 20232 yr Not sure what I did wrong. Also, I've always used WimScript.ini when running capture after a sysprep. Is it necessary to do this when copying the partition? D:\ThinApps\WinNTSetup\Cpy2VHD.cmd 23:53 WinCopy Q:\ --> Z: config: D:\ThinApps\WinNTSetup\WimScript\WimScript.ini Failed to copy Windows installation. WIMHost (wimlib) error 0x44: The requested operation is unsupported Total elapsed time: 1:14 mins 23:54 Edited November 7, 20232 yr by click-click
November 8, 20232 yr Author 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.
November 8, 20232 yr Sorry, I was using a batch file to create the vhdx and to do the Wincopy. As it turns out I did not consider diskpart not finishing its' script if it could not create the vdisk. This was causing the wimlib error because nothing got mounted by diskpart. I finally got it working by deleting the vhdx before running the batch, but the copy takes extremely long to finish. 19 min. compared to 7 min. doing a restore. Edited November 8, 20232 yr by click-click
November 9, 20232 yr Author 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.
Create an account or sign in to comment