Windows 10 Release 1511

So I would need to apply the 1511 update on all computers afterwards? This update took over an hour to install

Hello,

You are getting this message because ImageAssist runs Sysprep already. You have the Windows 10 version that was released last July and applied a system upgrade 1511. This changes the version of the OS and ImageAsssit will not accept it. This will cause ImageAssist not to work while running the Sysprep process. If you don't have the latest version of Windows 10 TH2, then I would attempt to capture that image on a VM NOT connected to the web.

I wanted to correct this previous post. For an immediate solution, the Upgrade will still have to be applied afterwards. I have talked to our engineering group and got some further clarification. The upgrade has been made available by Microsoft. However, we are currently working on getting the media for Windows 10 TH2 available to our customers. We hope to have a solution within the next couple weeks for the distribution of the media across lines of business.

Unfortunately yes the Upgrade would have to be applied afterwards. Microsoft has not made Windows 10 TH2 available for distribution yet due to licensing. We should have TH2 available in the next 30 days for distribution once Microsoft provides it to us.

I've spent well over 12 hours trying to make the MS Win10 64-bit Enterprise build 1511 install to work.  This install is not an upgrade, as it is installed directly from the MS Win10 Enterprise 64-bit ISO I downloaded recently from MS.

I dont install any updates by leaving the computer disconnected from the network.  I've used this laptop before to create a working image with the original windows build, and using the same apps and configuration, nothing has changed other the original install media to the more recent MS build 1511.

The sysprep runs fine.  Unlike the failure I was experiencing when I tried imaging an upgraded version.

However, when trying to restore the captured 1511 build, it injects the latest CAB file fine apparently, but in the subsequent reboot it goes by the device setup and then gets stuck indefinitely on a Getting Ready message with a spinning circle.  I left it like this overnight after several CFI rebuilds and restore attempts and it was the same except for a cmd window that was left open over that same screen, no other change and no hard drive activity throughout.  Before that it seems to accept the latest cab file and everything, but when windows gets to the Getting Ready message it gets stuck.

I'm doing things according to Dell's directions as I did when I built other images correclty in the past.  Is this a problem with build 1511 (again, not upgraded, but original install media build 1511 from MS) and Dell Image Direct not working?

Hi QADAUS - 

Were you able to make it past the issue with reboots?  It sounds like you may have been running into an issue with legacy v. UEFI booting.  I've seen this same scenario when the BIOS was not configured correctly.

Thank you,

Tyler