Re: CRACK Windows Assessment And Deployment Kit (ADK) For Windows 8

0 views

Skip to first unread message

Message has been deleted

Benedicte Mansukhani

unread,

Jul 9, 2024, 5:43:25 PM7/9/24

to khusweicarpo

When I look at the download link for the ADK ( -us/windows/hardware/windows-assessment-deployment-kit) there is the following disclaimer: Note: You must use Windows 10, version 1607 with this version of the ADK.

CRACK Windows Assessment and Deployment Kit (ADK) for Windows 8

Download File https://lpoms.com/2yN4LT

I'm somewhat confused by this as it implies (to me) it only runs on Windows 10 1607, but that can't be right since you would not run ConfigMgr on Windows 10. So I'm just wondering if this is the correct location for the ADK for Windows 2012R2?

I've read the link previously but don't see anything stating the ADK isn't supported on 2012r2 (server). If its not supported on 2012R2 (server) then the only other option would be Windows 10, but I don't imagine anyone would be running Configmgr on Windows 10 or that its even supported or able to be installed.

You probably noticed that Microsoft release a new version of Windows ADK for Windows 11 last month (May 2022), the 22H2 version. One major change in this version compared to the 21H2 version of the kit is that x86 boot images are no longer included. In this post you learn about what this means for ConfigMgr and MDT Lite Touch environments.

Update October 5, 2022: There is now a fix available for the MDT Lite Touch script issue. Thank you, Daniel, for bringing that to my attention. See the official docs here for a workaround: -issues.md

According to the official documentation covering the new features for the 22H2 version, Microsoft only mentions improvements for the Windows Performance Recorder (WPR) and Windows Performance Analyzer (WPA). The what's new information don't even mention the fact the x86 boot images are removed from WinPE, but there is a note about the on the Download and install the Windows ADK page.

When doing a file comparison between 21H2 and 22H2 I did notice there was a new optional component for WinPE: The winpe-hsp-driver.cab file. This seems to be support for the new Microsoft Pluton Processor. Below is a listing of the new files in 22H2 (when installing only the OSD components and WinPE):

First of all, ConfigMgr 2111 now supports the 22H2 version of Windows ADK for Windows 11. If you upgrade Windows ADK to this version in your ConfigMgr environment, ConfigMgr won't be able to reload or update the x86 boot image anymore. Not the end of the world if you don't need it, but still.

Like ConfigMgr 2203, MDT Lite Touch does not have official support for the new ADK either. In fact, MDT, which has not been updated since 2020, don't even have official support for anything Windows 11, even though it happens to work just fine.

In my testing the x64 22H2 boot image does not seems to work with MDT Lite Touch, even if following the instructions later in this post to prevent the Deployment Workbench from crashing. When starting an MDT Lite Touch Deployment using Windows 11 ADK 22H2 the HTA-based wizard is not very happy.

If you upgrade Windows ADK to 22H2 on your MDT server, the Deployment Workbench will crash once you click on the Windows PE tab in the deployment share properties. To prevent that from happening, simply copy in the x86 boot image structure from an earlier version of the ADK to the install folder.

My guess would be a missing network driver in WinPE, or an older network driver preventing a newer native driver to be used. Try boot up the device on a boot image without any added drivers, and see if you get an IP address. If you don't, try to add only the driver for the network card in the 7480 and see if that works.

Windows ADK for Windows 11 21H2 and Windows ADK for Windows 11 22H2 are both supported to deploy Windows 10 and Windows 11. Most of our customers are currently Windows ADK for Windows 11 21H2 for their Windows 10 deployments. That being said, good old Windows ADK 2004 will happily deploy Windows 10 and Windows 11 as well. Microsoft just doesn't list that as being supported.

I don't see a problem here. Not supported only means Microsoft doesn't test MDT anymore for Windows 11. The command line tools from Windows ADK are still supported. If you run into an issue, simply run the same command line as MDT runs when working with support.

I got PXE to work via the native responder, but it's easier to just stick to Windows ADK for Windows 11 21H2 for now. Well tested, and works fine when deploying both Windows 10 22H2 and Windows 11 22H2.

I can't fix the Windows PE tab crash on the latest kit version. I guess my copy of x86 from the Windows 10 version isn't old enough? I tried copying it over but no dice. Tried making empty x86 folder. Tried turning off x86 etc.

Hi Joshua,
The article is a bit misleading, it's the support for running setup.exe from a boot image with is being deprecated. Something you should never do anyway. Support for normal boot image use (MDT/ConfigMgr, custom OSD) is still in there.
/ Johan

there is also a problem when importing windows 10 22h2 to deploymentshare
mdt recognize it as windows 10 unknown and there is an error when trying to create task sequence with this version of windows.

Copyright 2021 by Mirolus (the company behind deployment research). All rights reserved. No part of the information on this web site may be reproduced or posted in any form or by any means without the prior written permission of the publisher.