Jump to content


CaptHelpful

Established Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About CaptHelpful

  • Rank
    Newbie
  1. 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
  2. Update - I tried just updating the DP's on all the boot images I had, without doing the client update. Still got errors. I tried turning off the 2 images that were broadcasting PXE and still got the error. The fix - I changed the boot image that my TS was using for PXE (under properties > advanced tab) to the default image that was updated already. Fixed all my ills...
  3. I'm using SCCM 1710 and have been having the following error happen part way through the TS. This is from the SMSTS.log This link, https://support.microsoft.com/en-us/help/4096313/the-apply-driver-package-task-fails-with-error-80070057 says to update my Boot Images to my DP's and I've done that with my main PXE boot image, however I was a bit scared to go all the way. With such a large difference between the current ADK - 10.0.16299.0 - and the current production client ver. - 5.00.8577.1115 - I'm wanting some reassurance and guidance. I have several different Boot images, some of which are stored in the default directory ( \\servername>\SMS_<sitecode>\osd\boot\<x64>, which should mean they are being updated when I update SCCM) and others which are custom boot images. However, when I go to update the DP, an option for both types shows up that's not covered anywhere and I'm a bit nervous to go forward with. 1st, why is there such a large range on the default boot images? 2nd, I've done the update on my default boot image (without reloading to the current WinPE ver of the ADK) and still had the same error. Does that point to needing to reloading, or do I need to update all the boot images as well (I came into this environment after it had been set up already and are still using the previous TS.) 3rd, do I need to update any of the TS themselves after doing this update? I know some are using old MDK packages... Thanks for the help in advance.
  4. 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
×
×
  • Create New...