Jump to content


Sign in to follow this  
stones@fcisd.net

Cannot Apply Operation System

Recommended Posts

I am using SCCM current branch and a month ago before upgrade images were applying just fine.  No I get errors when applying operating system.  I have done all kinds of searching and cannot find an answer.  Below is partial log with error.

 

System root for target OS is C:\WINDOWS, System drive is C:    ApplyOperatingSystem    9/16/2020 5:22:48 PM    1748 (0x06D4)
OSArchitecture=X64    ApplyOperatingSystem    9/16/2020 5:22:48 PM    1748 (0x06D4)
OS version is 10.0 ( OS system file version found to be 10.0.18362.1 )    ApplyOperatingSystem    9/16/2020 5:22:48 PM    1748 (0x06D4)
Successfully loaded a source BCD boot system    ApplyOperatingSystem    9/16/2020 5:22:48 PM    1748 (0x06D4)
SetupNewOS: Loaded source boot system from target volume "C:\"    ApplyOperatingSystem    9/16/2020 5:22:48 PM    1748 (0x06D4)
!sBootDevicePath.empty(), HRESULT=80004005 (..\bootvolume.cpp,34)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
System partition not set    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Unable to find the partition that contains the OS boot loaders. Please ensure the hard disks have been properly partitioned
Unspecified error (Error: 80004005; Source: Windows)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Command line for extension .exe is "%1" %*    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Set command line: "bcdboot.exe" C:\WINDOWS /l en-US    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Executing command line: "bcdboot.exe" C:\WINDOWS /l en-US with options (0, 4)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Process completed with exit code 15250    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
uExitCode == 0, HRESULT=80004005 (..\bcdbooter.cpp,88)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Bcdboot failed! bcdboot.exe C:\WINDOWS /l en-US failed (15250)
stdout:
Failure when attempting to copy boot files.
stderr:
    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
TS::Boot::BcdBooter::InstallBootFilesAndConfigBCD (sTargetSystemRoot, this->defaultLanguage, sBootVolume), HRESULT=80004005 (installimage.cpp,1132)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Unloading offline SOFTWARE registry hive    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Unloading offline SYSTEM registry hive    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
SetupNewOs(&pBootSystem), HRESULT=80004005 (installimage.cpp,1943)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Configure(), HRESULT=80004005 (installimage.cpp,2121)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Installation of image 1 in package FC10001B failed to complete.. 
Unspecified error (Error: 80004005; Source: Windows)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
installer.install(), HRESULT=80004005 (installimage.cpp,2187)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Closing image file C:\_SMSTaskSequence\Packages\FC10001B\Win10_1903_Reg.wim    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
ReleaseSource() for C:\_SMSTaskSequence\Packages\FC10001B.    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
reference count 1 for the source C:\_SMSTaskSequence\Packages\FC10001B before releasing    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Released the resolved source C:\_SMSTaskSequence\Packages\FC10001B    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia, g_RunFromNet ), HRESULT=80004005 (applyos.cpp,513)    ApplyOperatingSystem    9/16/2020 5:22:54 PM    1748 (0x06D4)
Process completed with exit code 2147500037    TSManager    9/16/2020 5:22:54 PM    1032 (0x0408)
 

Share this post


Link to post
Share on other sites

Make sure that the hard disk partitions are checked. This partition is set as the boot partition.
In the SCCM OSD, only bios is recognized as the first boot method of a certain hard disk.
Otherwise, an error will occur in the application operating system and the WIM image package cannot be released
If there are two hard disks, disk number 0 HDD and disk number 1 SSD, you need to install the operating system to the SSD, pay attention! ! ! The bios sets the HDD hard disk as the first boot hard disk first.

Then in the task sequence step, the disk 1 partition step must be set as the boot partition, which prevents IT technicians from manually adjusting the bios settings, which is suitable for automated OSD.
The traditional MBR boot method to install the operating system is affected by this,
UEFI is not affected by this rule.
See if it is caused by this problem.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...