Search the Community

2020-02-12 18:16:46, Info SYSPRP ========================================================2020-02-12 18:16:46, Info SYSPRP === Beginning of a new sysprep run ===2020-02-12 18:16:46, Info SYSPRP ========================================================2020-02-12 18:16:46, Info [0x0f004d] SYSPRP The time is now 2020-02-12 18:16:462020-02-12 18:16:46, Info [0x0f004e] SYSPRP Initialized SysPrep log at C:\WINDOWS\system32\sysprep\Panther2020-02-12 18:16:46, Info [0x0f0054] SYSPRP ValidatePrivileges:User has required privileges to sysprep machine2020-02-12 18:16:46, Info [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\WINDOWS\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything2020-02-12 18:16:46, Warning SYSPRP WinMain: File operations pending2020-02-12 18:16:46, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'2020-02-12 18:16:46, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'SHUTDOWN'2020-02-12 18:16:46, Info [0x0f003d] SYSPRP WinMain:Displaying dialog box for user to choose sysprep mode...2020-02-12 18:16:48, Info [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.2020-02-12 18:16:48, Info SYSPRP RunDlls:Running platform actions specified in action file for phase 32020-02-12 18:16:48, Info SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null>2020-02-12 18:16:48, Info SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml2020-02-12 18:16:48, Info SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>2020-02-12 18:16:48, Info SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD642020-02-12 18:16:48, Info SYSPRP ActionPlatform::LaunchModule: Executing method 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll2020-02-12 18:16:48, Info CSI 00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.651_none_5f2896f458eff373\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND2020-02-12 18:16:48, Info CSI 00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.651_none_5f2896f458eff373\wcp.dll' : got STATUS_SUCCESS2020-02-12 18:16:48, Error SYSPRP Sysprep_Clean_Validate_Opk: Audit mode can't be turned on if there is an active scenario.; hr = 0x800F09752020-02-12 18:16:48, Error SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll; dwRet = 0x9752020-02-12 18:16:48, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml; dwRet = 0x9752020-02-12 18:16:48, Error SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x9752020-02-12 18:16:48, Error [0x0f0070] SYSPRP RunDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x9752020-02-12 18:16:48, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep cleanup internal providers; hr = 0x800709752020-02-12 18:16:48, Info [0x0f0052] SYSPRP Shutting down SysPrep log2020-02-12 18:16:48, Info [0x0f004d] SYSPRP The time is now 2020-02-12 18:16:48

I've run out of steam and patience - after doing a all this for the 2nd time in 2 days, I've run into a repeating sysprep error that doesn't look like an error to me. I've done my regular routine on removing appxpackages, and not seeing any sticking in this setupact.log If you can tell me what to fix I'll praise you as the IT god you are! 2018-04-30 01:15:29, Info CBS TI: --- Initializing Trusted Installer --- 2018-04-30 01:15:29, Info CBS TI: Last boot time: 2018-04-29 23:00:52.808 2018-04-30 01:15:29, Info CBS Starting TrustedInstaller initialization. 2018-04-30 01:15:29, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:4 2018-04-30 01:15:29, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5 2018-04-30 01:15:29, Info CBS Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:6 2018-04-30 01:15:29, Info CBS Ending TrustedInstaller initialization. 2018-04-30 01:15:29, Info CBS Starting the TrustedInstaller main loop. 2018-04-30 01:15:29, Info CBS TrustedInstaller service starts successfully. 2018-04-30 01:15:29, Info CBS No startup processing required, TrustedInstaller service was not set as autostart 2018-04-30 01:15:29, Info CBS Startup processing thread terminated normally 2018-04-30 01:15:29, Info CBS TI: Startup Processing completes, release startup processing lock. 2018-04-30 01:15:32, Info CBS Starting TiWorker initialization. 2018-04-30 01:15:32, Info CBS Lock: New lock added: TiWorkerClassFactory, level: 30, total lock:2 2018-04-30 01:15:32, Info CBS Ending TiWorker initialization. 2018-04-30 01:15:32, Info CBS Starting the TiWorker main loop. 2018-04-30 01:15:32, Info CBS TiWorker starts successfully. 2018-04-30 01:15:32, Info CBS Lock: New lock added: CCbsWorker, level: 5, total lock:3 2018-04-30 01:15:32, Info CBS Universal Time is: 2018-04-30 06:15:32.287 2018-04-30 01:15:32, Info CBS Loaded Servicing Stack v10.0.16299.15 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.15_none_2c4b8d3b386eed8e\cbscore.dll 2018-04-30 01:15:32, Info CSI 00000001@2018/4/30:06:15:32.287 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffd0c364519 @0x7ffd0cfeb8b6 @0x7ffd0cfebd78 @0x7ff67bad2c32 @0x7ff67bad35b8 @0x7ffd2cef6d13) 2018-04-30 01:15:32, Info CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:8 2018-04-30 01:15:32, Info CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9 2018-04-30 01:15:32, Info CBS NonStart: Set pending store consistency check. 2018-04-30 01:15:32, Info CBS Session: 30662730_2766797669 initialized by client Sysprep, external staging directory: (null), external registry directory: (null 2018-04-30 01:17:32, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

I'm trying to create a new .wim capture of an updated Windows 10 1709 (Hyper-V VM). I created capture media w/ SCCM, ran it on NewBuild18v2 (my VM), it reboots, say username and password are wrong and shows defaultuser0 as option - can’t log into it. Administrator is listed, takes password and then gets stuck at “Just a Moment”. was able to get a cmd window w/ F12 and entered this via regedit - [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE]"SkipMachineOOBE"=dword:00000001 Thanks to Frank Maxwitat from TechNet. It was able to restart and login but left me w/ a broken machine - start button wouldn't work, right click on task bar won't work, run works but I'm still stuck. I took the .wim it saved to my share and placed it in my TS and get an error (0x80070400) element not found. I don't know if it's a bad unattended file, but I've included it and the STSMS log for those who read them better than I. Main question - is there a way to salvage the VM and do another sysprep and capture, or do I need to start over? Thanks in advance for the help! smsts.log unattend.xml

Hello all, It is nice to find this forum, hopefully I can get through this issue with your help. I've been working through issues with the Sysprep and Capture TS, and after a few days of struggling through I've come to a real head scratcher. I can get the TS to execute and fully capture and create the WIM file, however the file is not being put where specified in the Capture Image question of the wizard. The BDD file is even logging that its putting it in the correct directory, but nothing. I can't find it anywhere on the MDT server in either of the deployment shares that exist in the file system. <![LOG[About to run command: "\\ntfs-mdt\BuildShare$\Servicing\X64\dism.exe" /Capture-Image /CaptureDir:D: /ImageFile:"C:\BuildShare\Captures\WIN10-PLEDGE-BASE.wim" /Name:"WIN10CAP10DDrive" /Compress:MAX /ConfigFile:"\\ntfs-mdt\BuildShare$\Tools\X64\wimscript.ini" /ScratchDir:"D:\MININT\Scratch"]LOG]!><time="16:32:23.000+000" date="10-03-2017" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup"> <![LOG[Using the backup path: C:\BuildShare\Captures\WIN10-PLEDGE-BASE.wim]LOG]!><time="17:05:53.000+000" date="10-03-2017" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup"> <![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="17:05:53.000+000" date="10-03-2017" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup"> Do the logs suggest its storing it locally? Why does it use the UNC and then revert to C:\ locally? Has anyone run into this before? I'm at wits end and web searches have not proved to be successful on this one. Thanks,

I'm doing a quick build and capture with Windows 10 Build 14393 (1607) in which I have a script that removes some of the default installed apps. It's being done with System Center. In regards to the Contact app, it's now able to be uninstalled as a package. $Packages = (Get-WindowsPackage -Online).PackageName ForEach ($Package in $Packages) { If ($Package -like "*ContactSupport*") { Remove-WindowsPackage -Online -PackageName "$Package" -NoRestart } } It is removed with no issues, won't appear in the start menu for any users, but Sysprep will fail because of it. [setuperr.log] Failed to remove staged package Windows.ContactSupport_10.0.14393_......... Failed to remove apps for the current user: 0x80070002 When I log in to the VM after it fails, Windows.ContactSupport only appears if I run "Get-AppxPackage -AllUsers" where it says it's still staged {S-1-5-18 [s-1-5-18]: Staged} by NT AUTHORITY\SYSTEM If I even try to run powershell.exe as SYSTEM and now try Remove-AppxPackage it just fails like it used to and can't be resolved. Has anyone run in to this and able to fix it? Or should I just stop trying to remove "Contact Support" and leave it like the last Windows 10 OS builds had to be?

Hi I followed the following walkthrough(http://www.vkernel.ro/blog/creating-an-offline-mdt-deployment-media) and was able to boot into litetouch on the vm I am trying to sysprep and capture. However when I get to language selection the section is blank and I cannot choose a language, halting me from continuing. This is my first tome using MDT. Any tips?

I'm attempting to capture a Windows 10 Enterprise x64 1607 Current Branch image with a basic load of applications preinstalled. Every attempt has ended with image capture failed error code 0x00004005 I've gone so far as to try recreating the Capture media and attempting to capture Windows directly after an install on the VM with no other applications installed, and have received the same message from SCCM. The problem looks to be Sysprep not completing, but I can't seem to figure out why. A sysprep on a fresh install of Windows immediately after install on a new VM shouldn't fail, but for me, it does. Any help would be greatly appreciated. smsts.zip

so here is my issue. i am trying to create a updated image to deploy. i created the updated image and deployed it but when i do it doesnt auto join my domain and add my default profile. im assuming that its not completing the sysprep at some part, either when i capture the new image or when its running on the task sequences. my old capture works just fine but when i try the new one it wont. the task sequence is identical on both. on the new image when it installs, it still has the administrator profile from the OS i used the capture the image which is what im thinking its not doing the sysprep on the capture but im new at this and still learning so im not sure. neither the capture or the install give me an error. here is the link to the logs files. https://drive.google.com/drive/folders/0B86v2JnOCBOwbURrZm50eHZHekk?usp=sharing on the server it created two folders. 1. MININT-AI01HTE 2. MININT-EL0BL5G on the ones in the past that work it creats a folder with the computer name i gave it, but that isnt happening. im also putting in the log files on the laptop in the MININT folder. and the unattanded file. does anyone have an idea on how i can fix this?

Why does my sysprep keeps on going wrong. Can anyone help me out? smsts.log

​Hi Guys, first time posting here so apologies if this is the wrong spot. I've recently swapped out the older win 10 image for the 1511 image in our production task sequence. Has anyone been experiencing slower install times post sysprep and capture? I run through my task sequence which is fine. But then due to management direction I need to make huge wims to capture all the apps. I do a manual sysprep which then finish it off with a dism capture. After applying the new wim I start up the build it gets stuck on the "getting ready" screen for ages. I've looked at the setupact.log and the "SYSPRP Provisioning packages are applied successfully" task took approximately 1 hr 30 minutes. ​I did hack my way through getting 1511 building though. Because currently in production our adk is using 8.1. So I needed to build a custom boot winpe with not the latest adk 10 1511 but the previous one using dism to add components. ​

I have an issue with OSD Captures in 2012, since we cant import 2007 wim files. The computer will init the TS and go through all of it except the sysprep portion. That fails out. I have the logs from the client with some very non descriptive errors. The OS install doesnt look like its done before sysprep kicks in. smsts.log smsts-20140812-162414.log

I have a PC I'm trying to capture an image of. Windows was setup and deployed with an SCCM 2012 OSD Task Sequence. When I sysprep it, the mini-setup asks for all the questions one would expect, except for the Computer Name. This occurs even with NO answer file at all. I've scoured the PC looking for any conflicting answer file, but have found none. What am I missing?

I've read in previous posts about adding sysprep information (specifically updateinstalleddrivers=yes) to the "Apply Operating System" task. Is that done by checking the "Use an unattended or Sysprep answer file for a custom installation" box? That would make sense, but it's looking for a package, not just a bare file. However, if I try to create an application or package for deployment, it's looking for an msi file. Do I have to create an msi file that contains only the sysprep.inf file? If so, how do I create that msi file without having Wise, InstallShield, etc.?

Hi, I am trying to create a wim file using sysprep and imagex. However when it comes time to boot into windows pe on my virtual machine, i cannot do this. I have tried buring the pe file to an ISO and booting the vm from this, but no joy. What is the best way to do this? Thanks

Hello, We are trying to get SCCM to deploy a bare metal image to a new model laptop in our fleet. We have had issues adapting our existing WIM, task sequences and drivers to this model, so we have instead opted to build Windows XP on this machine manually, install required drivers and then use a SCCM USB capture stick to capture to a WIM file. I have completed this process and captured to a WIM file and I’ve deployed this captured WIM to another machine and found it needs refinement. I was hoping to power on the template laptop from which I captured my image and continue working on it, but instead I find that now when I try to boot into Windows, it seems to think Windows doesn’t exist and is running “mini setup” instead, prompting for a Windows CD key, etc. Do you know whether the capture process is meant to affect the template machine like this? i.e. Should capturing a given machine revert that machine to a ‘blank slate’ state?

Hello, Anyone really figure out during Windows 7 sysprep to be prompted for a computer name and have it join your domain? I can have the machine stop and prompt for machine name but won't join domain. I used My Sysprep Tool, but don't trust it and typing in your password is in clear text, but it does work. I have tried to delete the line from the xml file but still doesn't prompt for computer name. Anyone have a working XML file to stop and ask for computer name then join it to the domain, while syspreping ?

Couple of issues that I can't quite remember when dealing with sysprep. 1) I have a couple images that aren't to be joined to our domain, yet when I set <JoinWorkgroup>WORKGROUP</JoinWorkgroup> in sysprep.xml AND in WDS I select "Do not join the client to a domain after an installation", it still ends up connecting to the domain. 2) I'm noticing in the registry, the original computer name that had been sysprepped and captured was still showing up. I used: sysprep.exe /oobe /generalize /shutdown I can't recall if this is just how it happens or if it's supposed to be like that.