WSIM requires 6.3.9600.16384 of Windows ADK

I will get this error message
This application requires version 6.3.9600.16384 of Windows ADK. System.ComponentModel.Win32Exception (0x80004005): Unknown error (0xc142011f)...
when I try to create a catalog file from my install.wim (Win8.1 Ent x64). My Version is
6.3.9600.16411.
Source:
http://www.microsoft.com/de-de/download/details.aspx?id=39982

I have what appears to be the same problem. This is using the install.wim from the MSDN WS2012R2 ISO with no modifications. The ADK is 8.100.26866, installed on Windows 8.1 Pro x64.
The log file contains the following: 3:21 PM :
This application requires version 6.3.9600.16384 of the Windows ADK.
Install this version to correct the problem
3:24 PM :
3:24 PM : Windows SIM was unable to generate a catalog. For troubleshooting assistance, see the topic: 'Windows System Image Manager Technical Reference' in the Windows ADK User's Guide.
3:24 PM :
3:24 PM : System.ComponentModel.Win32Exception (0x80004005): The parameter is incorrect
Server stack trace:
at Microsoft.ComponentStudio.ComponentPlatformInterface.WimImageInfo.PreCreateCatalog()
at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageInfo.CreateCatalog()
at Microsoft.ComponentStudio.ComponentPlatformInterface.CatalogCreatorImpl.CreateCatalog(OfflineImageInfo offlineImageInfo)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.ComponentStudio.ComponentPlatformInterface.ICatalogCreator.CreateCatalog(OfflineImageInfo offlineImageInfo)
at Microsoft.ComponentStudio.CatalogGenerator.CreateCat(ProgressDialog pd, Object o)
Any help would be appreciated... I've run out of ideas.

Similar Messages

WSUS 3.2 SP2 with KB2720211 and later KB2734608 rebuilt as WSUS 6.3.9600.16384. Will clients connect back OK after initial Sync to parent server?

Hello all, after many iteration of trying to fix 11 DSS running Windows 2008 R2 WSUS 3.2 SP2 sync issues with parent USS, we have decided to gradually move towards WSUS 6.3.9600.16384 on Windows 2012 R2.
I have already built a Windows 2012 R2 WSUS server (which will eventually replace the current 2008 R2 WSUS 3.2 SP2 master server) The sync is OK. There was no error on the data base side or anything.
The idea now is to gradually pick one DSS, rebuild it with Windows 2012 R2 WSUS service, and sync it with newly built and to be main primary server. The fact that I actually picked up a working WSUS 3.2 and rebuilt it with WSUS 6.3, will the clients still
talk back and connect? Or this version uses totally different update engine..in that case, how is it all going to work?
Shahidul

The fact that I actually picked up a working WSUS 3.2 and rebuilt it with WSUS 6.3, will the clients still talk back and connect?
Theoretically, yes; but in practicality, probably not.
Almost certainly your original WSUS v3 server was installed to the Default Web Site (port 80). WSUS v6 servers default to their own v-root on port 8530, so at a minimum you will need to reconfigure the GPO that tells the clients where to find their WSUS
Server. However, once you do that, the clients will register automatically.
The second part of this question relates to target groups.
If you're using Client-Side Targeting and you've created the groups on the new WSUS Server, the clients will automatically register in their policy-assigned groups.
If you're using Server-Side Targeting, you'll have to use the console to reassign the clients from "Unassigned Computers" to their correct target group(s).
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

This application requires version 6.3.9600.16384 of the Windows ADK. Windows 8.1 PRO OEM

Hi,
i am trying to sysprep a machine and i need to create the unattended xml file.I downloaded the Windows ADK for Windows 8.1 (update) and need to generate the answer file.Whenever i select the "install.wim" file from my Windows dvd (copied
to a writeable destination) , it gives me an error : "This application requires version 6.3.9600.16384 of the Windows ADK." .
I already found a forum post regarding this issue (https://social.technet.microsoft.com/Forums/en-US/69cd6ddd-fab6-4986-bd70-52ce894f37c2/creating-unattendxml-for-windows-8?forum=mdt)
, saying that the Windows ADK for 8.1 PREVIEW is needed but this link is removed from the website.
Can i still download this version somewhere or what is the solution?I already tried to slip in some update packages in the wim file (following this link : https://technet.microsoft.com/en-us/library/dn622020.aspx
) but no result, it seems that the version installed on my machine is not compatible with the newest 8.1 ADK.
I already tried to sysprep the machine with /oobe /generalize /shutdown (without an unattend xml file) , but when i reboot the system i get an error "windows could not parse or process the unattend answer file for
pass [specialize]. a component or non-list settings is specified more than once in the answer file".
What is the solution for this problem ?
F.

The link you presented above is a mess.
The idea of going back to the "PREVIEW" version of the ADK makes no sense to me, unless.. you are running a preview version. Which is silly.
Please be aware that there are *DIFFERENT* sub-build versions of the Windows 8.1. My version of the ntoskrnl.exe shows build 6.3.9600.17630.
Please be aware that there are also different versions of the Windows 8.1 ADK. If you are unsure if you have the latest version, please uninstall the ADK, and download again from MSFT.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

I have an airport extreme and my computer runs Microsoft windows XP Media Center Edition 2005. I receive an error message saying " airport requires that your computer is running windows xp sp3 or windows vista sp1 or newer"...why?

i have an airport extreme and my computer runs Microsoft windows XP Media Center Edition 2005. I receive an error message saying " airport requires that your computer is running windows xp sp3 or windows vista sp1 or newer"...why?

It is required to be able to connect. Download SP3 here. http://www.microsoft.com/download/en/details.aspx?id=24
I Hope I Was Able To Help You Or Solve Your Question.
Simmm
3/12/2012
If Someone Helped You, Click
"This Helped Me"
If Someone Solved Your Question, Click
"This Solved My Question"

Adobe photoshop lightroom requires that your computer is running windows 7 or later

when i try to install lightroom 5 on my pc i get this message "adobe photoshop lightroom requires that your computer is running windows 7 or later". i have a windows 7 pc. can anybody help me?

Install Service Pack 1 for Windows 7
http://www.adobe.com/products/photoshop-lightroom/tech-specs.html
http://windows.microsoft.com/en-au/windows7/install-windows-7-service-pack-1

Itunes wont inport anythig it show listings but comes up with error ocurred while converting (song title ) the required file cannot be found using windows 8

itunes wont inport anythig it show listings but comes up with error ocurred while converting (song title ) the required file cannot be found using windows 8

iTunes cannot convert protected WMA tracks. There may also be problems if it can't get full access permissions. What exactly are you trying to do when the error occurs?
tt2

When i try to open itunes on windows keeps saying apple application is required to run itunes error 2 windows error 2

when i try to open itunes on windows keeps saying apple application is required to run itunes error 2 windows error 2

You could try downloading and installing 7-Zip (free) and downloading a fresh copy of the iTunes installer, unpack the installer into its components using 7-Zip then try a standalone install of AppleApplicationSupport. It may still fail to install but if so you may get useful error messages as to why not.
tt2

Bootcamp requires that your computer is running Windows 7?

After installing Windows XP SP2 on a 30GB FAT32 partition I can't get past a message that says 'Bootcamp requires that your computer is running Windows 7'. I have ejected the Windows XP disc and insteted the Mac OS X install disc to install the Bootcamp drivers and then see this message. I have a new MacBook Pro 13" with the 2.3GHz dual-core Intel Core i5 and 320 GB harddrive. Am I doing something wrong? Or is XP excluded from Bootcamp?
Thanks in advance for any help.

XP & Vista are no longer supported, you will have to install Win7, and when you do your partition will need to be larger (50G min) and formatted as NTFS

AirPort requires that your computer is running Windows 7 SP1 or newer, AirPort requires that your computer is running Windows 7 SP1 or newer

AirPort requires that your computer is running Windows 7 SP1 or newer, AirPort requires that your computer is running Windows 7 SP1 or newer

There is a version for earlier releases..
But you should update your win7 to sp1 anyway.

Bug in HyperV Integration Services 6.3.9600.16384 ?

Hi,
I just deployed a VM (Generation 1) hosted on a 2012 R2 Datacenter-Hypervisor. For deployment I used WDS and the VM had a "Legacy Network Adapter". Deployment works fine. After deployment I installed Hyper-V Integration Services (Version 6.3.9600.16384).
Then I shutdown the VM, removed the Legacy network adapter and added a "normal" network adapter and started the machine again. I noticed that the network-connection is down.
When I check the properties it says "This device cannot start. (Code 10)".
I tried to uninstall the Adapter, I tried to remove the adapter and add a new one - no change. Even I redeployed the VM completely new...same problem...
Does anyone know this issue?
Regards
Miranda

Hi just a couple of question, what O.S version is you VM running. ? what system did you build your VM on ?/
Try removing and re-installing the integration services on the Virtual Server. make sure it completes with no errors.
you might need to force your VM to detect the new HAL.
To change the HAL
Open the System Configuration utility (MSConfig.exe). To do this, click
Start, click Run, type msconfig, and then click
OK.
Click the Boot tab, and then click Advanced options.
Select the Detect HAL check box, click OK, and then restart the virtual machine.
Important
Changing the HAL will usually trigger an operating system reactivation.

Require list of all events for Windows Server 2008 Active Directory

Hi all,
I require list of all events for Windows Server 2008 Active Directory. Event Log name for Active Directory log is "Directory Service".
Regards,
SR

Hi,
Thanks for your posting.
Do you mean you want to list all Active Directory logs into one file named “Directory Services”?
If that, it’s hard to achieve. There are kinds of Active Directory logs stored in different locations and they have different file formats. It’s hard
to collect them into one file.
Active directory records events in the directory services log in Event Viewer. By default, Active Directory records only critical error events. To instruct Active
Directory to record other events in the directory services log, we need to modify registry.
For more information please refer to following MS articles:
Active Directory Diagnostic Logging
http://technet.microsoft.com/en-us/library/cc961809.aspx
How to configure Active Directory diagnostic event log
http://support.microsoft.com/kb/314980
Lawrence
TechNet Community Support

What are the Minimum Requirement to Install OBPM 11g In Windows ??????

can some one tell us the Minimum System Requirement to Install OBPM 11g In Windows ??????
Thanks
Network 22

Hi,
The following are the basic requirement:
1) Windows machine: 2 GB of memory
2) Windows machine: Disk space 3GB
3) Browsers: Firefox 3.x or IE 7.x
Software for Windows Machine
JDeveloper 11.1.1.3
On the Windows machine, open a browser and go to the OTN download site for JDeveloper 11.1.1.3 .
In the Windows Install row and the Studio Edition column, click the link for the filename given. This is an .exe file.
Accept the license agreement when prompted and finish the download.
Save this file anywhere you wish.
This version of the JDeveloper binary contains the required version of the JDK. You will download two additional JDeveloper extensions from within JDeveloper after installing it.
Please find the help in the following link:
http://st-curriculum.oracle.com/obe/fmw/obpm/11g/r1/install/installing_obpm11g.htm
Bibhu

Hardware requirements for sap bw3.5 in windows environment

Pls help me the hardware setup(harddisk,ram etc) required for SAP BW3.5 in windows environment.
thanks in advance..
Regards
Ganesh

Hi,
HDD : 100GB
RAM : 1 GB
regards,
Raju

Update DISM in WinPE, Windows ADK for Windows 8.1 Update

Windows ADK for Windows 8.1 Update, creates WinPE with DISM version 6.3.9600.16384.
Latest build of Windows 8.1 Pro Build 9600, dated 22/11/2014, has DISM version 6.3.9600.17031.
Have run the Windows ADK setup again, but says NO Updates available.
Have created listings of all the DISM files in WinPE and Windows 8.1, but reluctant to copy files across, as I assume that registration / registry changes are also required.
Does anyone know how we can update the version of DISM in WinPE to 6.3.9600.17031?
Thanks, John

DISM files in Windows 8.1...
WIN-P1V1BFHNLTV C:\Windows\dism*
Sun 19/04/2015 19:02:12.11 Administrator RNDIR 1.5.2.49 10-Apr-2015 C:\Windows\dism*
C:\Windows\Logs\DISM
C:\Windows\Logs\DISM\dism.log
C:\Windows\Prefetch\DISM.EXE-D9E524DA.pf
C:\Windows\Prefetch\DISMHOST.EXE-598C5A9E.pf
C:\Windows\System32\Dism
C:\Windows\System32\Dism.exe
C:\Windows\System32\DismApi.dll
C:\Windows\System32\Dism\DismCore.dll
C:\Windows\System32\Dism\DismCorePS.dll
C:\Windows\System32\Dism\DismHost.exe
C:\Windows\System32\Dism\DismProv.dll
C:\Windows\System32\Dism\en-US\DismCore.dll.mui
C:\Windows\System32\Dism\en-US\DismProv.dll.mui
C:\Windows\System32\en-US\Dism.exe.mui
C:\Windows\System32\en-US\DismApi.dll.mui
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism\Dism.Format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism\Dism.psd1
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism\Dism.psm1
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Dism\Dism.Types.ps1xml
C:\Windows\SysWOW64\Dism
C:\Windows\SysWOW64\Dism.exe
C:\Windows\SysWOW64\DismApi.dll
C:\Windows\SysWOW64\Dism\DismCore.dll
C:\Windows\SysWOW64\Dism\DismCorePS.dll
C:\Windows\SysWOW64\Dism\DismHost.exe
C:\Windows\SysWOW64\Dism\DismProv.dll
C:\Windows\SysWOW64\Dism\en-US\DismCore.dll.mui
C:\Windows\SysWOW64\Dism\en-US\DismProv.dll.mui
C:\Windows\SysWOW64\en-US\Dism.exe.mui
C:\Windows\SysWOW64\en-US\DismApi.dll.mui
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism\Dism.Format.ps1xml
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism\Dism.psd1
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism\Dism.psm1
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\Dism\Dism.Types.ps1xml
C:\Windows\WinSxS\amd64_microsoft-windows-d..anagement.resources_31bf3856ad364e35_6.3.9600.17031_en-us_cac7f03ebc6b27c5\Dism.exe.mui
C:\Windows\WinSxS\amd64_microsoft-windows-d..cing-management-api_31bf3856ad364e35_6.3.9600.17031_none_97b32ab0331d7369\DismApi.dll
C:\Windows\WinSxS\amd64_microsoft-windows-d..ement-api.resources_31bf3856ad364e35_6.3.9600.17031_en-us_0393f46435b92988\DismApi.dll.mui
C:\Windows\WinSxS\amd64_microsoft-windows-d..ervicing-management_31bf3856ad364e35_6.3.9600.17031_none_4f9af566e17dbc2c\Dism.exe
C:\Windows\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_1c257853fe906c1a\DismCore.dll
C:\Windows\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_1c257853fe906c1a\DismCorePS.dll
C:\Windows\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_1c257853fe906c1a\DismHost.exe
C:\Windows\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_1c257853fe906c1a\DismProv.dll
C:\Windows\WinSxS\amd64_microsoft-windows-d..ment-core.resources_31bf3856ad364e35_6.3.9600.16384_en-us_02b013759532eb99\DismCore.dll.mui
C:\Windows\WinSxS\amd64_microsoft-windows-d..ment-core.resources_31bf3856ad364e35_6.3.9600.16384_en-us_02b013759532eb99\DismProv.dll.mui
C:\Windows\WinSxS\amd64_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_9ce1bd3c3df000d6\Dism.Format.ps1xml
C:\Windows\WinSxS\amd64_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_9ce1bd3c3df000d6\Dism.psd1
C:\Windows\WinSxS\amd64_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_9ce1bd3c3df000d6\Dism.psm1
C:\Windows\WinSxS\amd64_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_9ce1bd3c3df000d6\Dism.Types.ps1xml
C:\Windows\WinSxS\x86_microsoft-windows-d..anagement.resources_31bf3856ad364e35_6.3.9600.17031_en-us_6ea954bb040db68f\Dism.exe.mui
C:\Windows\WinSxS\x86_microsoft-windows-d..cing-management-api_31bf3856ad364e35_6.3.9600.17031_none_3b948f2c7ac00233\DismApi.dll
C:\Windows\WinSxS\x86_microsoft-windows-d..ement-api.resources_31bf3856ad364e35_6.3.9600.17031_en-us_a77558e07d5bb852\DismApi.dll.mui
C:\Windows\WinSxS\x86_microsoft-windows-d..ervicing-management_31bf3856ad364e35_6.3.9600.17031_none_f37c59e329204af6\Dism.exe
C:\Windows\WinSxS\x86_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_c006dcd04632fae4\DismCore.dll
C:\Windows\WinSxS\x86_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_c006dcd04632fae4\DismCorePS.dll
C:\Windows\WinSxS\x86_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_c006dcd04632fae4\DismHost.exe
C:\Windows\WinSxS\x86_microsoft-windows-d..ing-management-core_31bf3856ad364e35_6.3.9600.17031_none_c006dcd04632fae4\DismProv.dll
C:\Windows\WinSxS\x86_microsoft-windows-d..ment-core.resources_31bf3856ad364e35_6.3.9600.16384_en-us_a69177f1dcd57a63\DismCore.dll.mui
C:\Windows\WinSxS\x86_microsoft-windows-d..ment-core.resources_31bf3856ad364e35_6.3.9600.16384_en-us_a69177f1dcd57a63\DismProv.dll.mui
C:\Windows\WinSxS\x86_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_40c321b885928fa0\Dism.Format.ps1xml
C:\Windows\WinSxS\x86_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_40c321b885928fa0\Dism.psd1
C:\Windows\WinSxS\x86_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_40c321b885928fa0\Dism.psm1
C:\Windows\WinSxS\x86_microsoft-windows-d..nagement-powershell_31bf3856ad364e35_6.3.9600.17031_none_40c321b885928fa0\Dism.Types.ps1xml

SCCM 2012 RTM to SP1 Upgrade - Windows ADK 8.1

Hello,
I am after some advice. We have two physical locations containing a single SCCM 2012 primary site server in one location and distribution point server in the other location.
Both servers are also configured as DHCP Servers and DHCP scope options have been configured correctly to allow both DHCP and Windows Deployment Services to co-exist.
OSD was working fine, until I upgraded the primary site server to SCCM 2012 SP1. During the upgrade process, I installed Windows ADK 8.1 which would appear is not supported however no errors were reported during the upgrade process.
Issues I have encountered;
- I can no longer PXE boot with the following error 'PXE-E55: ProxyDHCP service did not reply to request on port 4011'
- The x:\remoteInstall\Boot\Fonts directory is empty suggesting the boots images were not finalised.
- When updating the distribution points with the boot images i get the following error via the wizard;
• The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4566;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"UKS0003B\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889
SMSPXE.log contains the following errors;
Failed to copy X:\RemoteInstall\SMSTempBootFiles\XXX00014\WINDOWS\Boot\PXE\wdsmgfw.efi to X:\RemoteInstall\SMSBoot\x86\wdsmgfw.efi
InstallBootFilesForImage failed. 0x80070002
Warning: Failed to copy the needed boot binaries from the boot image X:\RemoteInstall\SMSImages\XXX00014\WinPE.XXX00014.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)
Failed adding image X:\RemoteInstall\SMSImages\XXX00014\WinPE.XXX00014.wim. Will Retry..
The system cannot find the file specified. (Error: 80070002; Source: Windows)
Failed to read ADK installation root registry value
I am looking for some advice on the best way to rectify this issue. Options I am considering are as follows, however I am unsure of the outcome should I attempt these;
1 - Upgrade to SCCM 2012 R2 which supports ADK 8.1
2 - Uninstall Windows ADK 8.1, install 8.0
3 - Attempt to restore back to SCCM 2012 RTM using file system backups and SCCM backups.
Any help or suggestions would be much appreciated.

Thank you both for your replies and advice
The configMgr 2012 environment is primarily used for OSD, and software updates for Servers only.
I have followed Peter’ advice, and uninstalled WADK 8.1 and installed 8.0 and I am currently investigating errors within the SMSPXE.log, and I have seen other posts elsewhere within these forums
with the same issue with suggested solutions which I shall investigate.
With regards to DHCP on the ConfigMgr site servers – I could not agree with you more.
Unfortunately, my company use a third party DHCP solution which was incapable of supporting PXE-boot for OSD.
We were therefore required to have a separate Microsoft DHCP solution on the site servers to by-pass this issue.
The intention is to upgrade to Configmgr 2012 R2.
My understanding is that there is no direct upgrade process from SCCM 2012 RTM to R2, therefore I have upgraded to SP1 and would prefer all features are working correctly before progressing to R2.
Many thanks again,
Regards,
JohnRox

WSIM requires 6.3.9600.16384 of Windows ADK

Similar Messages

Maybe you are looking for