Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING SCCM Boot Image Failed to make a copy of source WIM file due to error 2

  • Thread starter Thread starter SAuty
  • Start date Start date
  • Replies Replies 2
  • Views Views 6K

SAuty

New Member
Messages
2
Reaction score
0
Points
1
Hi,
Just updated to ADK 2004 and having issues with the last step of updating distribution point boot image. My X86 boot image worked without issue, but the X64 image is giving the following:
Google isn't bringing up much, and the few things I have found are not helping.
Error: Update boot image:
• Microsoft Windows PE (x64)

Error: Windows ADK reload actions:
• Reload using Windows PE from the ADK version 10.0.19041.0

Error: Update actions:
• Add ConfigMgr binaries using Production Client version 5.00.9049.1010
• Inject prestart command line
• Add custom background
• Set scratch space
• Disable Windows PE command line support
• Add drivers

Error: Failed to import the following drivers:
• Intel(R) ICH7R/DH SATA AHCI Controller
• Intel(R) ICH7R/DH SATA RAID Controller
• Atheros AR8131 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
• 3Com Dual Port 1000-SX PCI-X Server NIC
• Intel(R) 82579LM Gigabit Network Connection
• Intel(R) PRO/1000 PT Dual Port Network Connection
• Intel(R) 82567LM-3 Gigabit Network Connection
• Intel(R) 82575EB Gigabit Network Connection
• Intel(R) 82580 Gigabit Network Connection
• Intel(R) 82567LM-2 Gigabit Network Connection
• NVIDIA nForce Networking Controller
• Realtek PCI GBE Family Controller
• AMD SATA Controller
• LSI Adapter, SAS2 2116 Meteor ROC(E) -StorPort
• NVIDIA nForce Serial ATA Controller
• AMD USB 3.0 Root Hub
• AMD USB 3.0 Host Controller
• Texas Instruments XHCI Controller
• Intel(R) ICH9M-E/M SATA AHCI Controller
• 3Com Dual Port 1000-SX PCI-X Server NIC
• Broadcom NetLink (TM) Gigabit Ethernet
• Intel(R) 82579LM Gigabit Network Connection
• Intel(R) 82580 Gigabit Network Connection
• Intel(R) 82599 Multi-Function Network Device
• E153ANC.DeviceDesc%
• Intel(R) Ethernet Connection I217-LM
• Intel Chipset SATA RAID Controller
• Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller

Optional components:
• Scripting (WinPE-Scripting)
• Startup (WinPE-SecureStartup)
• Network (WinPE-WDS-Tools)
• Scripting (WinPE-WMI)

Error: The wizard detected the following problems when updating the boot image.
• The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
• Description = "Failed to make a copy of source WIM file due to error 2";
• ErrorCode = 2;
• File = "..\\sspbootimagepackage.cpp";
• Line = 5426;
• ObjectInfo = "CSspBootImagePackageInst::preRefreshPkgSourceHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"CC100005\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
};

Any help greatly appreciated
 
Description = "Failed to make a copy of source WIM file due to error 2". ErrorCode = 2.
This is caused because the original driver source files that you added to the boot image no longer exist or have been moved. Driver injection for boot images happens every time you update the boot image and these drivers are pulled from the original import location and not the driver packages. Thus, you need to verify that the original driver location you imported drivers into ConfigMgr is still accessible and the driver files are still there.
 
Description = "Failed to make a copy of source WIM file due to error 2". ErrorCode = 2.
This is caused because the original driver source files that you added to the boot image no longer exist or have been moved. Driver injection for boot images happens every time you update the boot image and these drivers are pulled from the original import location and not the driver packages. Thus, you need to verify that the original driver location you imported drivers into ConfigMgr is still accessible and the driver files are still there.
Thanks, I guessed that might be the problem. The issue I have is I can't see the drivers tab anymore so I can't remove them. :(
 

Forum statistics

Threads
7,171
Messages
27,990
Members
18,297
Latest member
Kahnrym

Trending content

Back
Top