Windows AIK for Windows 7 SP1 Released

re: Windows AIK for Windows 7 SP1 Released

RAJEEV KUMAR SETHI — Mon, 22 Oct 2012 16:12:36 GMT

I installed Windows Vista SP1 on the current version of Windows Vista Business. The software downloaded and installed while I was working on it. Even approx.3 hrs. the update did not finish. Therefore, I re-started the machine thinking that the machine had stopped working. But, after restarting the machine, it did not start at all. It just showed 3.... bytes out of ...... installed. Now, the machine is not working. How to bring the machne to the working condition without loosing any data. Please help me. My mail-id is sethi.rajeevkumar@gmail.com. I am waiting for immediate solution from you.

re: Windows AIK for Windows 7 SP1 Released

DG — Thu, 07 Apr 2011 16:31:29 GMT

Here is a link to explain the issue with PE 3.1:

blogs.technet.com/.../issue-with-mdt-2010-update-1-and-windows-aik-for-windows-7-sp1-supplement.aspx

re: Windows AIK for Windows 7 SP1 Released

Eric T — Tue, 08 Mar 2011 22:31:32 GMT

Can you please explain the small issue with WinPE 3.1 and WinRE being included in images? We bundle a semi-customized Windows RE that took a while to build -- what can we expect with this issue? Thank you!

re: Windows AIK for Windows 7 SP1 Released

Delfim — Tue, 01 Mar 2011 10:14:18 GMT

Hi,

Without updating WAIK, when i try to deploy a W7SP1 x86, i have the following error in LTIApply :

"the subsystem needed to support the image type is not present"

I updated MDT 2010 to Update 2010 Update 1 -> Problem still happens

I Updated the WAIK with this release -> Problem Fixed

Delfim.

re: Windows AIK for Windows 7 SP1 Released

Jim — Mon, 28 Feb 2011 20:02:38 GMT

Hi Michael

I had a Windows 7 SP1 (32 Bit) install image and a 2008 R2 SP1 (64 Bit) install image copied to my deployment share. When I tried to rebuild the deployment share it still attempted to use the original RTM images of these for the boot media. I reimported the SP1 files and tried again but no matter what I did, the deployment share rebuilt with the RTM images and not the SP1 images. I even tried to add a 64 Bit Win 7 SP1 image into the deployment share to see if that would help, but no such luck.

When I switched the control file the deployment share built out just like it always has in the past, only using the new WinPE files as the boot media. For me I'm not too picky as to what is booting (At least I've not seen any issue yet why one boot wim would work better then another) just as long as it boots and lets me install my boxes.

One other side note, when I repaired the AIK install that did not fix my issue. It still would not build out the LiteTouch files correctly. I even removed all of the SP1 install files, but the errors continued. I just figured I'd remove the whole AIK installation and reinstall the original and the updates. That worked and now everything seems happy again.

Thank you for taking the time to suggest these fixes. And thanks for helping provide MDT. It has been a great way for our test lab to automate OS deployments. We're using it in a lab with nearly 1300 machines and it gives us the flexibility we need to do our installs (much more flexible then previous disk image solutions).

Jim

re: Windows AIK for Windows 7 SP1 Released

Michael Niehaus — Thu, 24 Feb 2011 19:09:52 GMT

You can go to the "Programs" control panel to repair the Windows AIK install - that should put the original files back.

The errors you received appear to be caused by a mismatch between the WIM being used and the components being added. I'm guessing that you have a Windows 7 OS (RTM, not SP1) in your deployment share? It's probably using the WIM from there. You can also try modifying the Settings.xml file in the Control folder of your deployment share to set "Boot.x86.UseBootWim" and "Boot.x64.UseBootWim" both to "False".

I'll investigate more shortly, right now I'm on vacation :-)

-Michael

re: Windows AIK for Windows 7 SP1 Released

Jim — Thu, 24 Feb 2011 16:29:43 GMT

Oddly enough now that I've added this AIK into my environment I can no longer create litetouch wim files that work. When I rebuild my deployment share I get the following errors:

Deployment Image Servicing and Management tool

Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - Adding package WinPE-HTA-Package~31bf3856ad364e35~x86~~6.1.7601.17514

Error: 0x800f081e

The specified package is not applicable to this image.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Exit code = -2146498530

This then repeats for the following components:

winpe-scripting

winpe-wmi

winpe-mdac

If I then boot the LiteTouch wims that are created they boot up and give me a The Deployment Wizard was cancelled or did not complete successfully message. I never see my task screens or anything. If I revert back to the wim files that I created right before upgrading to AIK 3.1 then the deployment works like it should. Not sure what but something in this AIK file seems to have eaten my deployment workbench.

Any way to back off AIK 3.1?

re: Windows AIK for Windows 7 SP1 Released

JFD — Thu, 24 Feb 2011 08:22:04 GMT

(There is one small issue involving Windows 7 SP1, Windows PE 3.1, and having Windows RE included in your MDT-generated Lite Touch boot images, but if you don’t mind Windows RE not being there, you don’t need to worry about this.)

Hello,

Could we have more information about this please ?

Thanks

re: Windows AIK for Windows 7 SP1 Released

Tony Ellis — Thu, 24 Feb 2011 00:41:09 GMT

Looks like the process of creating a single wim from multiple wim does not work with Windows 7 with SP1. Any plans to update imageX so that process works

re: Windows AIK for Windows 7 SP1 Released

Michael Niehaus — Wed, 23 Feb 2011 20:39:14 GMT

It is possible to install SP1 into an image, then sysprep and recapture a new WIM. (SP1 can't be injected offline.)

If you have an automated image build process (something we encourage) then it's easier to download the "slipstreamed" image from the Microsoft Licensing website and use it to create a new image.

-Michael