tsolaaa

Hi guys, I'm officially stumped on what to do next. I have two images, one with Windows 7 SP1 OEM English and another with Windows 7 SP1 OEM German. The german image keeps failing during the build process when adding the new updates. My Anti-Virus (AVG Free) is turned off. WinTool Kit is running with admin privileges. I am running Windows 7 SP1. I am running WinTool Kit v1.5.2.16 There are no language packs installed. I have already tried to remove the update right before it gets to the part where it fails. I have tried reducing the amount (20 to 10 or so) I have tried selecting a single update to add. I have made sure the order is matching what shows on the windows update list. It just won't let me add any more updates than what is already integrated. If I put the reamining updates in the list, it fails on the first one, goes to the second and then gives me the "Aborting" error and doesn't continue. Any suggestions? Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. All rights reserved.C:\Program Files (x86)\WinToolkit>chcp 65001C:\Program Files (x86)\WinToolkit>Set SEE_MASK_NOZONECHECKS=1C:\Program Files (x86)\WinToolkit>"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\WinToolkit_Mount_F460AD59FA83F996EE63590FDF7A2B30" /Add-Package /PackagePath:"C:\Users\taylor_rocket_mbp00\Desktop\Windows Updates\german part 8\AMD64-all-ie11-windows6.1-kb3003057-x64_7f4fae04879f00ca018f9e3c87b51ffca7a83359.msu" /ScratchDir:"C:\Windows\WinToolkit_Temp\ScratchDir_9D2D00FB711DAD72209C064DB000A401" /EnglishDeployment Image Servicing and Management toolVersion: 6.3.9600.17029Image Version: 6.1.7601.18489Processing 1 of 1 - C:\Users\taylor_rocket_mbp00\Desktop\Windows Updates\german part 8\AMD64-all-ie11-windows6.1-kb3003057-x64_7f4fae04879f00ca018f9e3c87b51ffca7a83359.msu: An error occurred applying the Unattend.xml file from the .msu package.For more information, review the log file. Error: 0x800f0830Error: 0x800f0830DISM failed. No operation was performed. For more information, review the log file.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Program Files (x86)\WinToolkit>exitAnd here is my DISM log (part of it, I wasn't 100% sure what I needed to include. 2014-11-25 15:46:25, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.2014-11-25 15:46:25, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager2014-11-25 15:46:25, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.2014-11-25 15:46:25, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider2014-11-25 15:46:25, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager2014-11-25 15:46:25, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager2014-11-25 15:46:25, Info DISM DISM Transmog Provider: PID=5040 Current image session is [OFFLINE] - CTransmogManager::GetMode2014-11-25 15:46:25, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.2014-11-25 15:46:25, Info DISM DISM Provider Store: PID=5040 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider2014-11-25 15:46:25, Info DISM DISM Provider Store: PID=5040 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider2014-11-25 15:46:25, Info DISM DISM Package Manager: PID=5040 Processing the top level command token(add-package). - CPackageManagerCLIHandler::Private_ValidateCmdLine2014-11-25 15:46:25, Info DISM DISM Package Manager: PID=5040 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine2014-11-25 15:46:25, Info DISM DISM Package Manager: PID=5040 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine2014-11-25 15:46:25, Info DISM DISM Package Manager: PID=5040 Encountered the option "packagepath" with value "C:\Users\taylor_rocket_mbp00\Desktop\Windows Updates\Part 9\X86_AMD64_IA64-all-windows6.1-kb2978120-x64_58bd67b83022d9ba81879342f2ca787dc164b08e.msu" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine2014-11-25 15:46:25, Info DPX Started DPX phase: Resume and Download Job2014-11-25 15:46:25, Info DPX Started DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Ended DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Started DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Ended DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Ended DPX phase: Resume and Download Job2014-11-25 15:46:25, Info DISM DISM Provider Store: PID=5040 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider2014-11-25 15:46:25, Info DISM DISM Provider Store: PID=5040 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider2014-11-25 15:46:25, Info DISM DISM Provider Store: PID=5040 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider2014-11-25 15:46:25, Info DISM DISM Provider Store: PID=5040 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider2014-11-25 15:46:25, Info DISM DISM Package Manager: PID=5040 Attempting install from source location [%configsetroot%\Windows6.1-KB2978120-x64.CAB]. Full path [C:\Windows\WinToolkit_Temp\ScratchDir_3F4526A6B2BD8FA290369DCE47B5E254\D1203BE6-109C-4DF2-B4FC-7568748DCEAD\Windows6.1-KB2978120-x64.CAB]. - CPackageManagerUnattendHandler::Internal_InstallPackageFromSource2014-11-25 15:46:25, Info DPX Started DPX phase: Resume and Download Job2014-11-25 15:46:25, Info DPX Started DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Ended DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Started DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Ended DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Ended DPX phase: Resume and Download Job2014-11-25 15:46:25, Info CBS Opened cabinet package, package directory: C:\Windows\WinToolkit_Temp\ScratchDir_3F4526A6B2BD8FA290369DCE47B5E254\D1203BE6-109C-4DF2-B4FC-7568748DCEAD\, sandbox location: \\?\C:\Windows\WinToolkit_Temp\ScratchDir_3F4526A6B2BD8FA290369DCE47B5E254\3B9EF373-0EC6-45DF-B44A-59006D0F64D0\, cabinet location: \\?\C:\Windows\WinToolkit_Temp\ScratchDir_3F4526A6B2BD8FA290369DCE47B5E254\D1203BE6-109C-4DF2-B4FC-7568748DCEAD\Windows6.1-KB2978120-x64.CAB, manifest location: \\?\C:\Windows\WinToolkit_Temp\ScratchDir_3F4526A6B2BD8FA290369DCE47B5E254\3B9EF373-0EC6-45DF-B44A-59006D0F64D0\update.mum2014-11-25 15:46:25, Info DPX Started DPX phase: Resume and Download Job2014-11-25 15:46:25, Info DPX Started DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Ended DPX phase: Apply Deltas Provided In File2014-11-25 15:46:25, Info DPX Ended DPX phase: Resume and Download Job2014-11-25 15:46:25, Info DISM DISM Package Manager: PID=5040 No selectable features found. - CPackageManagerUnattendHandler::Internal_UnattendQueueSelectFeatures2014-11-25 15:46:25, Info DISM DISM Package Manager: PID=5040 Initiating Changes on Package with values: 4, 7 - CDISMPackage::Internal_ChangePackageState2014-11-25 15:46:25, Info CBS Appl: detect Parent, Package: Package_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0, Parent: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514, Disposition = Detect, VersionComp: EQ, ServiceComp: EQ, BuildComp: EQ, DistributionComp: GE, RevisionComp: GE, Exist: present2014-11-25 15:46:25, Info CBS Appl: detectParent: package: Package_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0, related parent found: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385, which is not real parent2014-11-25 15:46:25, Info CBS Appl: detectParent: package: Package_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0, parent found: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514, state: Installed2014-11-25 15:46:25, Info CBS Appl: detect Parent, Package: Package_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0, disposition state from detectParent: Installed2014-11-25 15:46:25, Info CBS Appl: Evaluating package applicability for package Package_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0, applicable state: Installed2014-11-25 15:46:25, Info CBS Blocked system sleep; prior state: 0x800000002014-11-25 15:46:25, Error CBS The image has been damaged by an offline servicing failure and no further servicing is allowed. [HRESULT = 0x800f0830 - CBS_E_IMAGE_UNSERVICEABLE]2014-11-25 15:46:25, Info CBS Restored system sleep block state: 0x800000002014-11-25 15:46:25, Info DISM DISM Package Manager: PID=5040 Error in operation: (null) (CBS HRESULT=0x800f0830) - CCbsConUIHandler::Error2014-11-25 15:46:25, Info CBS Exec: Processing complete. Session: 5040_277654573, Package: Package_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x800f0830 - CBS_E_IMAGE_UNSERVICEABLE]2014-11-25 15:46:25, Error CBS Failed to perform operation. [HRESULT = 0x800f0830 - CBS_E_IMAGE_UNSERVICEABLE]2014-11-25 15:46:25, Info CBS Session: 5040_277654573 finalized. Reboot required: no [HRESULT = 0x800f0830 - CBS_E_IMAGE_UNSERVICEABLE]2014-11-25 15:46:25, Error DISM DISM Package Manager: PID=5040 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0830)\And lastly, a screenshot:

So I tried both methods above. I first put these files into the correct directory inside the \Sources\Scripts\...in the deployment folder. I also opened the install.wim and placed the files actually inside the c:\Windows\Setup\Scripts Both have no effect. There is nothing in Setupact.txt log either.... Maybe the UAC is preventing the applications from installing automatically?

Ah, found it. 7ZIP by Reaper wasn't completely removed by the WinToolKit App. There was two INF files hiding in the INF folder as well as an empty directory. Closed.

Hey Guys, Another question, I had some silent installers inside the WinTool Kit utility but I am installing the setup over PXE so this wasn't working. I ended up taking them out and using the "Delete Old Installers"option but for some reason when I try to install the OS at the end during the "Windows will close" it asks for a file. Specifically, a af.txt (Which belongs to the 7ZIP application I was trying to set as a silent install) I can't find where in the hell it is trying to install this from. Does anyone know what specific file WinTool Kit edits to run that install? Maybe this utility is just not removing it completely. I have already removed the "Wintool Kit" apps folder inside the image. There is no reference to it inside the $OEM$/$$/

I'm sorry, I don't fully understand. When I extract the ISO there is no "Windows" folder. There is a "Sources" folder. I'm using WinTool Kit to integrate everything and SERVA to deploy over PXE. I tried using the "Files" tab inside the application to place the SetupComplete.cmd file inside "C:\Windows\Setup\Scripts" but it is still not running. I have checked the log file and it doesn't even attempt to run it. Maybe it's placing the file after windows looks for it? I just tried placing the SetupComplete.cmd inside the "$OEM$\$$\Setup\Scripts" within the SERVA root directory and it still doesn't run. Where do I place all those registry entries and where do I place them inside the WinTool Kit App?

Thank you! But where exactly do I edit this? That path doesn't exist inside the extracted ISO I am using WinToolKit with. If this helps, I am using SERVA to deploy the installs over PXE. The SERVA root folder has "/$OEM$/$$" should I create the "setup/scripts/" and just add the batch file there and rename it to "SetupComplete.cmd" ?

Hey Guys, I need to inject a batch file into the all-in-one setup. I am using the ISO that is created by WinTool Kit over a PXE server so the silent installs set inside the app do not run like they should. Instead, I have told the app to place the files in the c:/ directory and then I would like to somehow have my install run my batch script to run the installs automatically. I have been unable to find any solutions yet. Maybe a custom .reg file inserted into the tweaks section that tells the OS to run the .bat file on the first startup? Anyone have any suggestions?

Found this out. I guess Windows 7 will just install the drivers that it needs and won't touch the rest. This makes things way easy!

Hey Guys, So I am using this tool (amazing by the way) to create a almost zero-touch install for some various machines. Now that I have had a week or two to play around with it and get it working the way I like, I want to create a new setup from scratch. Here is the thing, I am looking to create just one setup that will contain all the drivers for the three different machines I have. I am looking to see how exactly the driver integration works, when I integrate the drivers into the "All-In-One-Integrator" does that actually install the devices into the system, or is it just placing them somewhere in the OS and Windows will pick and choose from that folder what it actually needs? Or do you guys have a better solution? I was also thinking I could just put all the drivers into their respective folders somewhere in the C: drive and just run automate a script at the end that will install the correct drivers to the correct model of the machine. Thanks!