New
#70
Wow.....Should I report to Tomcat?![]()
Create a DISKPART script like shown below. DISKPART scripts are normal text files with .txt extension:
Code:create vdisk file=F:\W10PRO.vhdx maximum=51200 type=expandable attach vdisk create part primary format quick label="Windows" assign letter=W exit
This would create a 50 GB dynamically expanding VHD file as MBR disk, label it W10PRO.vhdx and save it on root of drive F, mounting it on host as drive W.
Run the script from your batch file with following command:
diskpart /s DRIVE:\FOLDER\SCRIPT.TXT
This is why I always create my native boot VHDs as MBR disks (the above script makes MBR disk, not GPT). No need to create any system partitions for upgrade in Hyper-V. To upgrade it, I only need to create a Hyper-V VM using that disk, boot from W10 install media or PE and run BCDBOOT to create boot records, and boot to Windows.
I never connect this VM to network, upgrading from ISO. This way WU will not get "confused", Windows on VHD now contains all your physical devices and drivers but when booted in Hyper-V, WU does not find those devices and keeps trying to update something that's not there.
Well said
Here you go Jimbo:
See video description and additional information in this post in Ten Forums video thread.
Kari
Can you guys check if vss is working ok
Run this from admin command prompt
wmic shadowcopy call create Volume='C:\'
Does it return error 0 or error 9 (and no Shadow ID) as it does on my laptop.