Unsolved
1 Rookie
•
18 Posts
0
1716
October 21st, 2020 10:00
Any issues with ImageAssist and Win10 20H2?
I just got done creating a VM using the new 20H2 release. I ran ImageAssist and it went through to the Sysprep with no issues. However, the Sysprep never finished. It ran for almost 2 hours. I finally shutdown the VM and I'm going to go back through it and make sure everything is good.
Just wanted to check in here before I dug too deep...
Thanks!
No Events found!
tkoscielniak
52 Posts
0
October 21st, 2020 11:00
Hello Wayne,
I just did a install with the latest Windows 10 2009 (20H2) and ran the latest DIA tool set on it. It went through without issue. Normally when sysprep fails, there is a DIA error that pops up. Make sure that the VM has plenty of hard drive space (100gb or more) and the system running the VM has plenty of free drive space. If sysprep is failing, there should be a log in the c:\windows\system32\sysprep folder. Look for setuperr.log and setupact.log. Those files will normally tell you what the failure is.
dwestmoadm
1 Message
0
March 15th, 2021 19:00
I'm having a heck of a time with mine.
IA will not create a recovery partition and it fails to drop the image.
And the VMware machine I use for my image does not boot after it is captured.
I've recreated this thing a handful of times. I don't even know what to look for anymore.
G0aT
1 Rookie
•
8 Posts
0
March 17th, 2021 08:00
Hi Team, I am having one particular issue with Image Assist. I use Hyper-V to create my images (20H2). The latest Images that I have created have broken powershell. I cannot start powershell for some odd reasons. I also cannot run CMD as Administrator. I keep getting regasm.exe error 0x0000142.
I am trying to not update windows before I create the image to see if that will work. During image creation the software detects incompatible appX packages (SpotifyAB.SpotifyMusic) that could break sysprep and fixes it with a reboot.
I think that could be the reason why powershell does not work after the image is created.