Hello! This is my first post to this forum. I started using DIA this year as Dell advised us that future machines would need to be imaged using DIA. I successfully created a Windows 7 Enterprise image in January, and my colleague built a "lab" image as well, and uploaded both to Dell.
I also successfully built a "Version 1" or Beta build of Windows 10 Education. However, we decided we need to enable more of the privacy options by default, and I also wanted to tweak a few things, so I started trying to build a Version 2. However, I have not been successful in getting this to pass the Sysprep phase.
I started out by building on the same machine I had used for Version 1, a Latitude E6320. I figured I could just start from Version 1 and make my changes, and re-sysprep it. But I got errors like below. So I (TWICE) rebuilt the image from scratch, this time using a Parallels VM.
However this is the error I got when using the DIA capture tool with Sysprep checked:
At this point, this system is unusable. The Start menu button doesn't work, and most Run commands get the error "Device is not ready".
However, here is what is in the logs:
setuperr.log
SYSPRP Error 0x-2147216616: Failed to re-enable Compat-Gentel custom trigger.
SYSPRP setupdigetclassdevs failed with error 0
I tried searching for those errors but didn't come up with anything useful on Google.
I checked Auto_Capture_Prep_Tool.log, it's very long, but it ends in the same text as I already entered above.
And I'm unable to run regedit (Device is not ready error), and networking is disabled so I can't remote registry it either.
One note to make is that I am trying to build the image with as few Windows Store apps pre-installed as possible. I used some Powershell commands to remove unwanted apps. This is the resource I used for that:
I ran into some problems this past week with updated appx packages after running Windows updates on 1511 (TH2). Create a batch file with the following content and run before sysprepping. Worked for me.
I had a very similar issue myself last week. Windows 10 is very picky when it comes to running sysprep. I also removed several built in apps on my build just to have sysprep fail. What I ended up doing is setting the autoadmin login count to 1, then run a script to call a power shell to delete the apps post sysprep. and reboot. I did have to add several delays to make sure the script completed. Hope this helps.
I added a bat file to run in the runonce as below, it does a 80 second delay, then removes the apps:
@Echo off cls Echo "Removing built in apps, Please do not touch a key" start /wait Powershell.exe -executionpolicy bypass -command "c:\windows\panther\delay.ps1" cls Echo "Removing built in apps, Please do not touch a key" start /wait Powershell.exe -executionpolicy bypass -command "c:\windows\panther\app_remove.ps1"
I'll give that a shot. I already have a C:\Applications folder that contains post-install stuff.
One question, do you know how to get a Powershell Script to run directly from explorer? In order to use the script I linked to above, I had to first open powershell, then set-executionpolicy unrestricted and then run the script, and then set it back to restricted. I'd rather not have to do that every time I image a PC!
Well, I don't know what I'm doing wrong. This time I started from scratch again, installed Education 64-bit, installed Office 2016 32-bit, put in the product keys for both (Windows 10 won't even let you do your desktop theme customizations until you put in the product key!), did not install anything else other than DIA, only copied over my Applications folder to C:.
Also this time, I did not let the VM connect to the internet for updates, and I did not open powershell for any reason, I set up the scripts like you posted above in the post-install commands in unattend.xml.
I let DIA validate, install Dell_PE and run sysprep over night. This morning, I come in and I've still got the same error message.
JTremblay - You mentioned that you were originally using E6320. Did this same issue occur on the E6320, or only when you started using parallels as your build base? I presume this means that your host machine is a Mac? We have not tested ImageAssist in a parallels. More information here regarding building in a VM. Best practices for building your image in a Virtual Machine
OK, so I started over again, this time on the E6320 again. However, after working on it all day, sysprep still throws up with the same error (after chewing on generalizing for a good long time).
In order to even get sysprep to process, though, I had to run some powershell commands to remove those pesky store apps that Microsoft is shoving down our throats (Candy Crush, Twitter, etc.)
Basically there's a reg key you can add manually and to the unattend.xml to block these things from loading, but didn't come across this until later on in the build.
Still need help with the error I'm getting. Not sure if it's entirely related to the Windows Store or not. Why would the error be "sysprep.exe /export "c:\dell_pe_folder\bcd_store_save"? Is it exporting the bcd file? Why?
OK, I finally got it to pass sysprep and capture with DIA! I think the sticking point was the new version of DIA. I installed the same version I used back in January, and did not update it.
However, after deploying the image to another machine, I noticed that Windows' privacy options have everything defaulting to ON again (I want to make the image default to sending NOTHING to Microsoft/3rd parties)
DELL-Tyler M
Moderator
•
350 Posts
•
3 Points
45094
1
Posted May 6th, 2016 10:00
I ran into some problems this past week with updated appx packages after running Windows updates on 1511 (TH2). Create a batch file with the following content and run before sysprepping. Worked for me.
Echo Off
CLS
Echo Removing some Appx Packages which interfere with Sysprep
powershell -executionpolicy remotesigned Remove-AppxPackage -Package Microsoft.Appconnector_1.3.3.0_neutral__8wekyb3d8bbwe
powershell -executionpolicy remotesigned Remove-AppxPackage -Package Microsoft.People_10.0.2840.0_x64__8wekyb3d8bbwe
powershell -executionpolicy remotesigned Remove-AppxPackage -Package Microsoft.Getstarted_2.3.7.0_x64__8wekyb3d8bbwe
powershell -executionpolicy remotesigned Remove-AppxPackage -Package Microsoft.Office.OneNote_17.6131.10051.0_x64__8wekyb3d8bbwe
powershell -executionpolicy remotesigned Remove-AppxPackage -Package microsoft.windowscommunicationsapps_17.6308.42271.0_x64__8wekyb3d8bbwe
powershell -executionpolicy remotesigned Remove-AppxPackage -Package Microsoft.MicrosoftSolitaireCollection_3.3.9211.0_x64__8wekyb3d8bbwe
powershell -executionpolicy remotesigned Remove-AppxPackage -Package Microsoft.SkypeApp_3.2.1.0_x86__kzf8qxf38zg5c
:Complete