Jump to content

Search the Community

Showing results for tags 'boot.wim'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 4 results

  1. Hi There, We recently upgraded from SP1CU3 -> R2CU1 and are now having issues building machines using our OSD task sequence. First we tried using our existing x64 boot.wim (version 6.2.9200) - however our task sequence fails at the diskpart stage. We then noticed that the driver tab is missing from the Boot Images properties page - probably because the WIM was created by an older version of ADK. So then we tried using the boot image automatically placed into SCCM by the ADK8.1 install (6.3.9600.16384) in our task sequence. However this results in a WIndows8 BSOD screen with the er
  2. At first I attempted to add drivers to a specific boot WIM and then updated the DP but got an error. Researched the error couldn't find anything, so I decided to update one of the other boot WIMs which we have and same thing (this time I didn't even try to add drivers, for one of them I even deleted the drivers and then update the DP) Here is the error I get. Error: Boot image to update: MDT Custom PE Error: Actions to perform: Add ConfigMgr binaries Disable Windows PE command line support Add drivers Error: Failed to import the following drivers: Error: The wizard det
  3. I Set up SCCM 2012 RTM, and have been fighting with deploy and capture for a few days. I successfully imported an Operating System Installer I successfully created a task sequence I I was able to get the machine to PXE boot, and it almost loaded windows PE; however, I kept getting the following error message: Windows PE cannot start because the actual SYSTEM ROOT directory (x:\windows) is differrent from the configured one (x:\$windows.~bt\windows). This can be configured from dism.exe with the /set-target path command. please refer the documentation for more details I was
  4. Hi guys i recently had network driver problems with some new HP models (8200 elite and Z210) i was looking at having to slipstream the drivers into the win7 and server 2008 boot.wim. I was having some problems finding the right drivers to inject when i thought that the win8 pre-release iso would have a boot.wim in the sources folder with lots of new drivers already on. And it did... so no more using win7 and server 2008 boot.wim. Hopefully this will help anyone who has similar problems. Knowing my luck everyone has already been doing this and i've just been sleeping. :-) Regards Les
  • Create New...