Error Setting Windows Pe System Root
is different from the configured one (X:\$windows.~bt\Windows) I ran into the following error message on a new SCCM 2012 SP1 server using the default boot.wim files which come on the Windows 8 installation media. Windows PE cannot start because the actual SYSTEMROOT directory (X:\Windows) is different from the configured one (X:\$windows.~bt\Windows). This can be configured from dism.exe with the /set-targetpath command. Please consult the documentation for more details. Press the OK buttonor close this message to reboot. After doing a little research this is a common problem when using the default boot.wim WinPE4.0files from the Windows 8 installation media. You have two options to correct this, the first is using DISM and using the /set-targetpath command to change the command to X:\WINDOWS as per the error message above. The second is using the boot.wim files which come with the Deployment and Imaging Tools. Simply load the Deployment and Imaging Tools Environment shell and run the following commands: copype x86 D:\Sources\OS\BootFiles\x86 copypeamd64 D:\Sources\OS\BootFiles\amd64 Here is an example of what it will look like as it extracts: The boot.wim file will be located under x86\media\sources for the respective operating system architecture you extracted, as shown in the following screenshot: If you use the boot.wim files from the Deployment and Imaging Tools you will not experience this problem and with any luck, PXE clients should boot straight into the SCCM configuration screen. Make sure you don't forget to Distribute the boot images and update the distribution points. Note: Make sure you restart the Windows Deployment Services Server service after changing boot files. Posted by Clint Boessen at 10:57 PM Labels: SCCM 1 comment: Donald BrownFebruary 28, 2016 at 8:07 PMwindows 10 product key , product key windows 7 ultimet , how to buy windows 7 product key from microsoft , get free licence key of ms visio 2010 promotional offer , free win 7 key , outlook mail product key 2010 , windows 8.1 professional key , genuine windows 7 oem product key , l82a7lReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Clint Boessen [MVP] clint.boessen@avantgardetechnologies.com.au Clint Boessen's Blog Clint Boessen Perth, Western Australia, Australia Microsoft Infrastructure Engineer MVP, MCSE, MCSA, MCTS, MCP MCITP: Enterprise Messaging Administrator MCITP: Enterprise Messaging Administrator 2010 MCITP: Server Administrator MCITP: Enterprise Administrator TS: SCOM My TechNet Posts Join My RSS Feed View my complet
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: MDT 2010 DISM DISM was unable to set the system root (target path) for the Windows PE image Solution Accelerators > Microsoft Deployment Toolkit Question 0 Sign in to vote Hi All, I have been trying to use MDT for the past six months for my organization and each time it is a new problem. After successfully http://clintboessen.blogspot.com/2013/10/windows-pe-cannot-start-because-actual.html creating the shares and working with them for almost a month, suddenly while updating the upload share with new drivers I get this error message "DISM was unable to set the system root (target path) for the Windows PE image so deployment cannot be updated." I tried to remove the drivers, and then update did https://social.technet.microsoft.com/Forums/en-US/0af35b3b-4e2a-4373-90af-284b71ebee2b/mdt-2010-dism-dism-was-unable-to-set-the-system-root-target-path-for-the-windows-pe-image?forum=mdt not work. I tried to check for the permissions and I am the admin in the machine so that was not a problem. I tried to see if the folders were write protected, they were not. I deleted the wim files and tried to recreate them, did not work. I uninstalled AIK and installed the latest version. Did not work. I uninstalled MDT and reinstalled. Did not work. So, any ideas what I should do from here. I am really at the edge here because if some system fails, I have absolutely no way to re-image it back with our custom image. Any other processes, or any suggestions on how to solve this would help. ========================================================================================== Additional info - CustomSettings file: [Settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipAppsOnUpgrade=YES SkipCapture=NO SkipAdminPassword=YES AdminPassword=*** SkipProductKey=YES SkipDomainMembership=YES ComputerBackupLocation=NETWORK BackupShare=\\cypher\X\Capture$\Captures BackupDir=%OSDComputerName% ========================================================================================= Bootstrap file: [Settings] Priority=Default [Default] DeployRoot=\\CYPHER\Capture$ UserID=Administrator UserPassword=**** UserDomain=***.***.***.*** ========================================================================================== Any further info shall be provided upon request. Thank you. Thursday, Feb
Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Error: systemroot http://reboot.pro/topic/12118-error-systemroot-folder/ folder Started by Wizardsden , Jul 29 2010 09:43 PM Please log in to reply 10 replies to this topic #1 Wizardsden Wizardsden Members 5 posts https://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/topic/dpsccm/dpsccm_r_troubleshooting_winpe.html United States Posted 29 July 2010 - 09:43 PM I finally got my Multi7 PE to build successfully, but when I boot it I get error setting an error that reads "WindowsPE cannot start because the actual SYSTEMROOT folder (X:\Windows) is different than the configured one (X:\$windows.~bt\windows). this can be configured from DISM.exe with the /Set-TargetPath command." How do I resolve this? thanks for the assist Wizardsden Back to top #2 vvurat vvurat Frequent Member Advanced user 317 posts Posted error setting windows 29 July 2010 - 09:59 PM HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion "systemroot" and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\winpe "path" values should be same i think. paths should be somewhere there or you can google there is answer for it i didnt try but can be Dism /image:C:\winpe_x86\mount /Set-TargetPath:X:\$windows.~bt\ or Dism /image:C:\winpe_x86\mount /Set-TargetPath:X:\ or Dism /image:C:\winpe_x86\mount /Set-TargetPath:X:\Windows One of them should work But if you built it dism probably not function because will not be servicable. Need manually edit registry. I couldn't find winpe value but working values for me. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "SystemRoot"="x:\\Windows" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion] "CommonFilesDir"="x:\\Program Files\\Common Files" "DevicePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\ 00,74,00,25,00,5c,00,69,00,6e,00,66,00,00,00 "MediaPathUnexpanded"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,\ 6f,00,6f,00,74,00,25,00,5c,00,4d,00,65,00,64,00,69,00,61,00,00,00 "ProgramFilesDir"="x:\\Program Files" "ProgramFilesPath"=hex(2):25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,\ 00,69,00,6c,00,65,00,73,00,25,00,00,00 hex values will turn normal values when you import it. Back to top #3 Wizardsden Wizardsden Members 5 posts United States Posted 29 July 2010 - 11:01 PM OK, so I changed [X:\$Windows.~bt\Windows] to [X:\Windows] in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion "systemroot" and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\winpe "InstRoot" now when I boot up I get the exact same error except it says the
it is likely that you simply do not have the appropriate network drivers installed, which prevents the machine from communicating with Configuration Manager. Check your driver catalog to ensure you have the right network drivers available and installed into the boot image, and update the boot image to your distribution points. Additional network or storage drivers might be needed in the boot image to enable the WinPE boot to function correctly. You should add those through Drivers in the Operating System Deployment node. The right drivers have been added to the boot image, but are not loadingThe original boot.wim file (WinPE boot image) created during Configuration Manager installation is copied and modified with IBM-specific drivers and other files. Your task sequences that use the IBM Deployment Pack must use this boot image or the tools might not work properly. Check to make sure the image into which you loaded the drivers is the same image being used by the task sequence. This is a common error for administrators who maintain multiple boot images. Servers will not boot using PXEPXE is an extension of DHCP, which uses a broadcast type of communication. Broadcast communication uses standard timeout values that are not readily changeable. As a result, a computer waits for a default timeframe to receive a DHCP or PXE response before timing out and causing a failure condition. Each time a server is rebooted, it must renegotiate the connection to the switch. Some network switches arrive configured with default settings that might incur connectivity delays. That is, the settings on the switch might cause a DHCP or PXE timeout because they fail to negotiate a connection in time. One of the features that can be affected by this issue is Spanning Tree Protocol (STP). STP is a protocol that prevents loops and provides redundancy within a network. A networking device using this algorithm might experience some latency as it collects information about other network devices. During this period of information collection, servers might boot to PXE and time out while waiting for a response from Windows® Deployment Services. Disa