Buggy client restore - error c000000e winload.exe

Looks like the bare metal client restore is a big buggy
Scenario - old SSD 256GB, restore to brand new 500Gb SSD
Old Partitions: RESTORE(no drive letter), OS C: (bitlocked)
After restore: RESTORE(C:), OS (D:)
Windows won't boot with error c000000e winload.exe
Booted into Windows repair mode (off Windows 8 CD)
- repair windows states it has  no idea how to fix it
- went into command line mode and used diskpart not exactly sure what I did, but it included resetting drive letters
       select volume 1
       remove
      select volume 2
      assign letter=C
- still won't boot
- re-ran repair mode. this time it fixed it and windows boots
The system is now happy and all files seem to be there
Conclusion: The partition attributes aren't being restored correctly, but the contents are ? 
I don't know if this is SSD specific, but something is definitely broken

Hi,
Based on the error code you posted c000000e, i checked with my inernal tool and found the following information
C:\Users\v-yanwen>err.exe c000000e
# for hex 0xc000000e / decimal -1073741810
  STATUS_NO_SUCH_DEVICE                                         
ntstatus.h
# A device which does not exist was specified.
# as an HRESULT: Severity: FAILURE (1), FACILITY_NULL (0x0), Code 0xe
# for hex 0xe / decimal 14
  ERROR_OUTOFMEMORY                                             
winerror.h
# Not enough storage is available to complete this operation.
# 2 matches found for "c000000e"
After we finished restoring the system we received the error code: Windows won't boot with error c000000e winload.exe. the reason we couldnt boot the system is because of one of the reasons as following:
# A device which does not exist was specified.
# Not enough storage is available to complete this operation.
Hope this inforamtion is helpfulfor you.
Thanks
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

  • Windows To Go windows/system32/Winload.exe corrupt or missing

    I have a windows to go hard drive and an error came up recently saying "windows/system32/winload.exe corrupt or missing". I made a recovery drive from normal windows 8 but it cant detect the windows to go hard drive (I think its because its only
    looking to internal hard drives). any help would be appreciated. thanks
    EDIT:: it should say winload in the title

    Hi!
    My name is Long.
    I've got the same issue like you and resolved that without repartition and reinstall window to to. 
    I will so you step by step what i did to resolve the error with winload.exe corrupt or missing. I hove that will help you resolve your problem too.
    As you known: Window to go run in a external harddrive with 2 partitions. The first Partition have 350 MB (FAT32, active partition and it contain boot files). The second partition have remaining space (contain window files).
    The first you need a computer have a working window 7 or 8 OS(recommend window 8 or highter)
    Plug your window to go hard drive to the window.
    Assign the first partition 350 MB by disk manager with letter Z: (normally the fist partition 350 MB is not mounted)
    Assign the second (contain windows files) with letter O:
    Delete all file in the partition Z:
    Open CMD and do the command.
           O:\windows\system32\bcdboot O:\windows /f ALL /s Z:
    Restart and boot to window to go.
    If you want to know why i did that, read below:
    (External Hard Drive = EHD)
    i found a lot of the suggests in the internet and did that.
    - I had try to replace the winload.exe file in the second partition but it not effect.
    - I replace the registry data in folder \windows\system32\config but it not effect.
    - I did some commands found in the internet but not effect too. (https://social.technet.microsoft.com/Forums/windows/en-US/1b2045b9-7fef-47f0-aea3-1e185fb7544c/fix-winloadexe-is-missing-or-corrupt-no-its-not)
    - System repair not work with EHD.
    After i did all the ways found in the internet, i think that, the problem is not due to winload.exe file.
    I read the tips to install window togo again and i try to reinstall the window to go without repartition.
    The install have 2 steps: 
    - 1: Partition and set active.
    - 2: Copy file and make boot
    I ignor the first step because my EHD have got 2 partitons like the tips. 
    I delete all file and folder relate to window except my pertional data (in the 2nd partition).
    I extract install.wim file and copy all to the 2nd partition. I restart and boot to EHD but it still got error.
    I'm used Bootice and check the MBR of EHD and i got unknown MBR. I think the the problem.
    So I used Bootice software, set MBR of EHD = Windows NT 6.x. and I
    Set PBR to 2 partitions are BOOTMGR boot record (FAT32/NTFS/ExFAT).  I restart and boot to EHD but it still got error.
    Next, I delete all file in 1st partition of EHD.
    I Open CMD and do the command 
    "o:\windows\system32\bcdboot o:\windows /f ALL /s z:"
    after that, i restart and boot to EHD and it worked. The window to go work perfect but i lost all settings :)
    So i think the 2nd partition and all files is ok. The problem is by the 1st partition.

  • Server 2012 R2 + MDT 2013 + WINLOAD.EXE error

    Hi All,
    After watching some videos on MDT 2013 integration with SCCM 2012 I have been testing some builds of Windows Server 2012 R2. The MDT 2013 integration is working well with Database look-ups providing the required rules for customsettings.ini. To coincide
    with the tests I am using the MDT 2013 Server Task Sequence Template.
    Unfortunately I am hitting an error whereby, when using the MDT Task Sequence the full Operating System fails to start with a:
    \Windows\System32\Winload.exe, 0xC000000F, File is Missing or Corrupt
    Note: This is happening when the full OS is starting up. This is not a WinPE startup issue.
    When I use a non-MDT Task Sequence, i.e. a typical task sequence we use for OSD the build process works OK. We still have MDT database integration working in that Task Sequence however.
    Some background info:
    As per our normal process we are using a Windows Server 2012 R2 Capture image. The reference machine was build and capture using a partition scheme of (Partition 1 - 500MB + No Drive Letter + Hidden, Partition 2 - 100% of disk - Drive C:\)
    This is a new SCCM 2012 R2 implementation and as such we installed CU3 as part of our build process. CU4 is yet to be applied.
    Our WinPE Boot Images are WinPE 5 with a build number of 6.3.9600.16384
    As we have an existing SCCM 2007 environment I am currently using USB Boot media to kick off the Task Sequence
    We are only considering a "New Computer" build scenario. The MDT 2013 Task Sequence already detects that because the "_SMSTSinWinPE" = True.
    In both Task sequences the Format and Partition step is as follows:
    Disk 0
    Standard(MBR)
    BDEDrive (Primary) - 499MB, Marked Active with variable BDEDrive assigned
    OSDisk (Primary) - 90GB variable OSDisk assigned
    In both Task sequences the Apply Operating System step is as follows:
    Using Captured Image
    Apply operating system from a captured image (Image 2-2)
    Apply image to Logical Drive (OSDisk)
    In both Task sequences the Apply Data Image step is as follows:
    Using Captured Image
    Image 1-1 (from the same captured image as shown above)
    Apply image to Logical Drive (BDEDrive)
    What has been done so far:
    Already eliminated driver packs as the problem occurs with and without them
    Have monitored the build process (during WinPE that is) to determine what disks and partitions are in play at that stage. The 500MB BDE and 90GB OS Partitions are created as expected. The Apply OS and Apply Data Image steps are applying to the correct partitions.
    I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /fixmbr + bootrec /fixboot
    I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /rebuildbcd
    I have tried toggling the "OSDPreserveDriveLetter" variable from True to False and back again. Based on my interpretation of the SCCM 2012 R2 + Windows Server 2012 drive letter issue this should be set to True so the capture image drive letters
    are preserved.
    I have disabled an UEFI Partitioning steps just as a precaution.
    There is no Bitlocker steps involved yet.
    I have trawled through the SMSTS.LOG. So far it looks OK to me:
    !--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: WinPEandFullOS TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Executing command line: tsenv.exe "OSDPreserveDriveLetter=True" TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Finished with error code 0 TSEnv 18/02/15 8:09:49 AM 728 (0x02D8)
    Process completed with exit code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    !--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Successfully completed the action (Set Variable for Drive Letter) with the exit win32 code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    MP server https://SOMETHING24.SOMETHING. Ports 80,443. CRL=false. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Setting authenticator TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set authenticator in transport TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Sending StatusMessage TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Setting message signatures. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Setting the authenticator. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 CCM_POST /ccm_system_AltAuth/request TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    In SSL, but with no client cert TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Request was successful. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: %_SMSTSMDataPath%\Logs TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Clear local default environment TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Updated security on object D:\_SMSTaskSequence. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a TS execution environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Save the current environment block TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Successfully save execution state and environment to local hard disk TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Start executing an instruction. Instruction name: Apply Operating System Image. Instruction pointer: 43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSCurrentActionName=Apply Operating System Image TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a local default variable OSDImageIndex TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Command line for extension .exe is "%1" %* TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Set command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Start executing the command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    !--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Expand a string: WinPE TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Executing command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
    Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Set command line: "OSDApplyOS.exe" /image:S0200034,2 /target:D: /runfromnet:False ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Found run from net option: 0 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Not a data image ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    ApplyOSRetry: ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    TSLaunchMode: UFD ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    'C:\' not a removable drive ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    The volume D:\ exists and is a local hard drive. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    The volume D:\ is using a valid file system. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Windows target partition is 0-2, driver letter is D:\ ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Verifying boot volume is NTFS. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    The machine does not have a local client cache. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    ResolveSource flags: 0x00000001 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    SMSTSPersistContent: . The content for package S0200034 will be persisted ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    DownloadOnDemand flag is true. Attempting to download content locally for Package S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Locations: Multicast = 0, HTTP = 2, SMB = 0. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Package Flags: 0x01000000 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Multicast is not enabled for the package. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Trying https://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    GetDirectoryListing() entered ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Initializing HTTP transport. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Setting Authenticator. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Set authenticator in transport ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Setting Media Certificate. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    WinHttp credentials set ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 PROPFIND /NOCERT_SMS_DP_SMSPKG$/S0200034 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    In SSL, but with no client cert ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Using thread token for request ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Request was successful. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    DAV response string is:
    <?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:displayname><D:getlastmodified>Tue, 10 Feb 2015 04:56:27 GMT</D:getlastmodified><D:getcontentlength>6814100762</D:getcontentlength></D:prop></D:propstat></D:response></D:multistatus> ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    List of files to be downloaded ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    File: http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    GetDirectoryListing() successfully completed ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 0-2147483646 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
    Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 2147483647-4294967293 ApplyOperatingSystem 18/02/15 8:10:40 AM 724 (0x02D4)
    Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 4294967294-6442450940 ApplyOperatingSystem 18/02/15 8:11:23 AM 724 (0x02D4)
    Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 6442450941-6814100761 ApplyOperatingSystem 18/02/15 8:12:14 AM 724 (0x02D4)
    Downloaded file from http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim to D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
    VerifyContentHash: Hash algorithm is 32780 ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
    Content successfully downloaded at D:\_SMSTaskSequence\Packages\S0200034. ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Opening image file D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Image file S0200034 version "2015-02-10" will be applied ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Starting to apply image 2 from dos-20150210.wim to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Wiping D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Set "D:\_SMSTaskSequence" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Set "%OSDStateStorePath%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Set "%_SMSTSClientCache%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Skipping D:\System Volume Information for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Skipping D:\_SMSTaskSequence for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Calculating expected free space. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
    Reporting deletion progress. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
    Successfully wiped D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Applying image to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Applying image 2 to volume D: ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
    Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
    The command completed successfully. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
    Successfully launched command shell. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
    Successfully applied image to D:\ ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
    OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
    Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
    Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
    CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
    System root for target OS is D:\Windows, System drive is D: ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
    OS Version is 6.3 ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
    Successfully loaded a source BCD boot system ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
    SetupNewOS: Loaded source boot system from target volume "D:\" ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
    BootLoader::restore: D:\, C:\ ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
    Saving bcd store to D:\_SMSTaskSequence\ApplyBootSystem\boot\BCD ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
    Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
    Set command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
    Executing command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
    Process completed with exit code 0 ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
    Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
    Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:12 AM 724 (0x02D4)
    Updating MountedDevices key in target system registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    OS volume after boot is: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Reading '\DosDevices\D:' value under MountedDevices in WinPE registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272081-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272089-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27208a-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27208b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27208c-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\X:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272095-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272098-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\G:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\H:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\I:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27209b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\DosDevices\J:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb2720cf-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb2720d2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb2720d5-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb2720e2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb2720f3-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '#{cb272126-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerating index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Enumerated index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
    Found value: '\??\Volume{cb272139-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Enumerating index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Enumerated index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Found value: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Enumerating index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Enumerated index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Found value: '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Data for value '\DosDevices\D:' matches data for value '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Done enumerating. Closing mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Closed mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Deleting MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Creating new MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Writing new values to MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Successfully updated MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Finished updating MountedDevices in target system registry (0x00000000) ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing up known name surrogate reparse points... ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\Documents and Settings] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\AppData\Local\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\AppData\Local\History] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\AppData\Local\Microsoft\Windows\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\AppData\Local\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\users\Administrator\Cookies] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
    Fixing junction point path [D:\use
    The fact that our normal Task Sequence works OK eliminates the Capture image and the WinPE boot images. It must be something I have not configured or configured incorrectly in the MDT task sequence.
    Any suggestions would be great.
    NSutton

    Hi,
    If I were you, I would Streamline the MDT Task Sequence to find the root cause.
    Moreover, please refer to the link below:
    How to fix Windows System32 Winload.exe Missing Or Corrupt 0xc000000f Error?
    http://winwiki.org/windows-system32-winload-exe-missing-or-corrupt-0xc000000f/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Ghost32 image on my X61s = error message with winload.exe and 0xc000000f

    hi
    scuse my poor english.
    i have a deployment to do with 200 notebooks : r61 & x61s.
    i create a WDS server with a boot.wim and a Ghost Solution Suite Server 2.5 with images of R61 & X61s on the same server 2003.
    i start my R61, boot on the F12, start WinPE, install the ghost image through the network, reboot the notebook and vista run normally, good.
    i start my X61s, boot on the F12, start WinPE, install the ghost image through the network, reboot the notebooks and i have a BOSD, a reboot, and this message : Windows\System32\winload.exe is crupt or missing, Status error : 0xc000000f.
    i try to repair with the vista dvd, bcdedit, /fixboot, /fixmbr, /rebuildbcd,... : same error
    i try with a new ghost image, same BOSD and error
    i try to install the ghost image since a USB hard disk, same BOSD and error
    perhaps there is a problem with the hardware of X61s ?
    thanks a lot for your responses !
    Message Edited by freenod on 08-21-2008 01:26 PM
    Message Edited by freenod on 08-21-2008 01:26 PM
    Message Edited by freenod on 08-22-2008 07:15 AM

    thanks for your response.
    i have to do a deployment with 200 notebooks for a Business School.
    the administrator of the Business School use a Vista Business OEM version for all the notebooks, R61 and X61s.
    they give to me a R61 and a x61s with Vista and a lot of softs installed.
    my job is to clone this two models and deploy the ghost image on the 198 others R61 and X61s :]
    on the disk there is two partitions : in first one IBM partition hidden, in second one Vista partition.
    i clone the entire disk of R61 with ghost solution suite 2.5 and my clone works perfectly with the R61.
    i clone the entire disk of X61s with ghost solution suite 2.5 and my clone give me a BSOD and a reboot.
    have you an idea ?
    thanks
    Message Edited by freenod on 08-22-2008 07:16 AM

  • Re: windows server 2012 - winload.exe missing or contains errors

    i've noticed mine is ver 4.3 and there's a ver 5 from their website, annoying because it said do i want to update the other day so it did and it seems it didn't bother doing ver 5 and was just a minor update

    i setup a 180 day trial of server 2012 r2 standard yesterday running as a vm in virtualboxwith less than 24 hours after doing so i find it now doesn't boot, which is really irritating as i configured it with some roles etc and don't want to do it all again if it's not going to be reliablewhen it trys to boot i get the following below, i've tried a few things with bootrec and bcdedit following some guides elsewhere but it's all useless and doesn't work so i need some help from people that actually know what they are talking about so i don't waste more of my time, hopefully the idiots that post junk that doesn't fix will have their posts removed from youtube somedayfile: \windows\system32\winload.exe
    status: 0xc0000001info: the application or operating system couldn't be loaded because a required file is missing or contains errors
    This topic first appeared in the Spiceworks Community

  • Windows server 2012 - winload.exe missing or contains errors

    i setup a 180 day trial of server 2012 r2 standard yesterday running as a vm in virtualboxwith less than 24 hours after doing so i find it now doesn't boot, which is really irritating as i configured it with some roles etc and don't want to do it all again if it's not going to be reliablewhen it trys to boot i get the following below, i've tried a few things with bootrec and bcdedit following some guides elsewhere but it's all useless and doesn't work so i need some help from people that actually know what they are talking about so i don't waste more of my time, hopefully the idiots that post junk that doesn't fix will have their posts removed from youtube somedayfile: \windows\system32\winload.exe
    status: 0xc0000001info: the application or operating system couldn't be loaded because a required file is missing or contains errors
    This topic first appeared in the Spiceworks Community

    i setup a 180 day trial of server 2012 r2 standard yesterday running as a vm in virtualboxwith less than 24 hours after doing so i find it now doesn't boot, which is really irritating as i configured it with some roles etc and don't want to do it all again if it's not going to be reliablewhen it trys to boot i get the following below, i've tried a few things with bootrec and bcdedit following some guides elsewhere but it's all useless and doesn't work so i need some help from people that actually know what they are talking about so i don't waste more of my time, hopefully the idiots that post junk that doesn't fix will have their posts removed from youtube somedayfile: \windows\system32\winload.exe
    status: 0xc0000001info: the application or operating system couldn't be loaded because a required file is missing or contains errors
    This topic first appeared in the Spiceworks Community

  • Equium A210-1C4: Winload.exe problem after using product recovery disk

    Hi There
    I Could really do with some help here. I have a Toshiba Equium A210-1C4 Laptop. Partitioned drive with Vista home premium service pack 4.0.
    Last night I used the product recovery disk supllied with the laptop to try and restore it back to its factory settings.
    and the end of the process I'm left with a cmd prompt box with X:\windows\system32\cmd.exe in the blue top bit stating:
    Error: imageX could not apply vista F:\05993xsp.swm Index 2 from ODD to C:\!
    Press any key to continue. That box dissappears then another one with Administrator: X:\windows\system32\cmd.exe in the blue top bit stating:
    waiting for ODD to become available...
    ODD Drive F: ready.
    check for medium in drive F:...
    Failed to initialise the raid class.
    No RAID - continue normally...
    X:\windows\system32>
    Now whenever the laptop tries to restart it just comes up with the error message:
    WINDOWS FAILED TO START. A RECENT HARDWARE OR SOFTWARE CHANGE MIGHT BE THE
    CAUSE
    FILE: \WINDOWS\SYSTEM32\WINLOAD.EXE
    STATUS: 0XC000000E
    INFO: THE SELECTED ENTRY COULD NOT BE LOADED BECAUSE THE APPLICATION
    IS MISSING OR CORRUPT
    Below I then have the option to esc or continue both with the same outcome of system trying to restart.
    The recovery disk has no repair option on it.
    please help, I haven't a clue.
    thanks

    Hi
    It looks like something went wrong during the Recovery procedure.
    Did you try to recover the notebook once again?
    If not you should definitely try this!
    You are right; the recovery disk hasnt a option for repair because the recovery disk is not the same like a MS Vista disk. The Recovery disk contains the image files (its a package) and the files contains the Vista, Toshiba drivers, tools and additional software.
    Therefore if something went wring during the recovery procedure, you will be not able to repair the OS installation but you have to run it again.

  • Windows Failed to Start (Winload.exe) After Resize Partition 0xc0000225

    Hi guys, I took a gamble and resized my system partition and now my Windows 8 can no longer boot up however,
    I can boot to Windows 7 and I am still able to see all my files in Windows 8 (i have a multiboot system)
    I try to copy winload.exe from windows 7 and put it in windows 8 but it doesn't allow me to do so, like it's
    locked or something. I also tried to repair/refresh/reset from the installation CD win 8 but no go
    I attached the ff error msgs, please help!!

    File: \Windows\system32\ntoskrnl.exe
    Status: 0xc000007b
    # for hex 0xc000007b / decimal -1073741701 :
    STATUS_INVALID_IMAGE_FORMAT ntstatus.h
    # {Bad Image}
    # The application or DLL %hs is not a valid Windows image.
    # Please check this against your installation diskette.
    # 1 matches found for "0xc000007b"
    The error means that your Windows 8 system was corrupted.
    Also the ntoskrnl.exe file was corrupt or missing.
    I suggest that you use Windows 8 media to restore Windows 8
    1.Insert a Windows 8 DVD, or a flash drive with the Windows 8 installation files on it, into your computer.
    Note: You're not installing or reinstalling Windows 8, you're just accessing Advanced Startup Options - no product key or license breaking required.
    2.Boot from the disc or boot from the USB device, whatever your situation calls for.
    3.From the Windows Setup screen, tap or click on Next.
    4.Tap or click on the Repair your computer link at the bottom of the window.
    5.Advanced Startup Options will start.
    6.When you select the Troubleshoot title,you'll see the Troubleshoot screen and see the Refresh your PC tile.
    7.Click Refresh your PC tile.
    Regards,
    Kelvin Xu
    TechNet Community Support

  • M8120N Desktop recovery winload.exe problem

    Back in 2007, I purchased an M8120N Multimedia PC.  During initial setup I created the recovery DVDs and have been playing happily with my system ever since.
    About 1 month ago, my C: drive started giving me "problems".  Checking the SMART info, I was told I was getting Read Errors and the drive needed to be replaced.  Given the system is more than 3 years old, getting a replacement from the vendor was out.  I had powered off the system in an effor to insure the system didn't fail for read errors.
    After getting ahold of a replacement drive, I started about the process of imaging my C: drive onto the new drive - CLICK, CLICK, CLICK (read error!)  My last system backup is too old to be useful - so restoring from that is out.
    I was able to boot my system using UBCD4Win and used a backup tool called DriveImage XML to make a complete backup of the drive - skipping past the 1 bad sector.  I have been able to use the same software to restore the backup onto my new drive.  Knowing that I had a bad sector, I *expected* problems on the first reboot.  When the system came up, I was told that the system had an error 0xc000000e when trying to load \windows\system32\winload.exe
    The error message from Windows indicates I should restart the computer and go into "Computer Repiar" to repair the problem.  Having booted from the recovery media, I see "Advanced" options to do things like Startup Repair and such.  I've tried Startup Repair and was told it fixed something.  On restart, I have the same error. 
    So I've gone and done much more research that seems to indicate I can do a BCD repair from a command prompt.  Looking thru the options available to me in Recovery Manager, I don't see any place where I can open a command prompt - and the boot message from Windows Vista itself seems to be geared towards "original" Microsoft DVD's.
    Any help is appreciated!
    Bob

    Using a clone from a hard disk with read/write problems is not going to work.
    You stated that you have the Recovery disc set. I recommend that you use the recovery disc set and install Windows on your new hard disk.
    Best regards,
    erico
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • 2012 R2 Essentials - Client Restore Service installation did not succeed.

    I have setup the computer backups successfully and I have verified that the workstations are creating the client backups. The issue I have now is trying to setup the Client Restore Service. Initially, it said I was missing the ADK which was expected since
    it was a fresh install so I used the link and it downloaded the ADK for Windows 8.1.
    Now when I try to setup the Client Restore Service in the wizard, after I click on Start it updates the status to "Customizing WinPE images..." and after 5 minutes, I get the following error:
    Client Restore Service installation did not succeed.
    Cannot customize the client restore image.
    The specified image file did not contain a resource section.
    If I click on Start to begin the process again, and I browse to the C:\Windows\Temp folder, I can see the two mounted folders for the customizing process:
    C:\Windows\Temp:
    GenBmrWinPETempPath: 8096c353-79cb-4d74-ae8d-3c287fdb735c : which remains empty and removes after failure.
    GenBmrWinPEMountPath: c32700c9-7391-4caf-9a7e-af420e96d327 : mounted WIM with directory structure but removes after failure when it unmounts.
    During the process, I also see the boot.wim in the following folder, "C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\8.100.25984_8.100.25984_6.3.9600.16384\0409\sources", with a filesize of 172,644KB.
    the GenBmrState.xml file contains the following information:
    <?xml version="1.0" encoding="utf-8"?><GenBmrJobExecutionInfo xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><Status>Idle</Status><LastStage>CustomizeWinPE</LastStage><OemImagesExist>false</OemImagesExist><AdkReady>true</AdkReady><ImageReady>false</ImageReady><MediaReady>false</MediaReady><WdsImageDeployed>false</WdsImageDeployed><Results><GenBmrJobResultPair><Key>Wds</Key><Value><Failed>true</Failed><Reason>CustomizeImageFailed</Reason><AdditionalErrorCode>0</AdditionalErrorCode><AdditionalErrorMessage>The
    specified image file did not contain a resource section.
    </AdditionalErrorMessage></Value></GenBmrJobResultPair></Results></GenBmrJobExecutionInfo>
    Does anyone know how to fix the "The specified image file did not contain a resource section" error?

    Thank you for your reply! Hopefully answering your questions will provide further input! I did look over the article you linked but that is the same procedure I followed except I receive the error after the ADK is installed and I click on the Start button
    which says it is "Customizing WinPE Images..."
    1. This is a Windows Server 2012 R2 Essentials installation from the Essentials media. It is not a role added to another edition of Windows Server 2012 R2.
    2. Yes, I have rebooted many times and the problem still persists.
    3. Yes, the WinPE-Setup.cab file does exist!
    4. I am copying an excerpt from the log that pretains to the error!
    Log:
    [13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmdskres.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\dmdskres.dll.mui".
    [13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmdskres2.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\dmdskres2.dll.mui".
    [13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmocx.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\dmocx.dll.mui".
    [13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmutil.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\mmc.dll.mui".
    [13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dmutil.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\mmc.dll.mui".
    [13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\en-US\hh.exe.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\hh.exe.mui".
    [13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\iepeers.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\iepeers.dll.mui".
    [13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\dwwin.exe.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\dwwin.exe.mui".
    [13336] 140705.213958.2249: GenBmr: Copying "C:\Windows\system32\en-US\diskmgmt.msc" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\diskmgmt.msc".
    [13336] 140705.213958.2405: GenBmr: Copying "C:\Program Files\Windows Server\Bin\ClientRestore\en-US\RestoreWizardResources.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\RestoreWizardResources.dll.mui".
    [13336] 140705.213958.2405: GenBmr: Copying "C:\Program Files\Windows Server\Bin\ClientRestore\en-US\WSSDriverSetupResources.dll.mui" to "C:\Windows\TEMP\c32700c9-7391-4caf-9a7e-af420e96d327\Windows\System32\en-US\WSSDriverSetupResources.dll.mui".
    [13336] 140705.213958.2405: GenBmr: Applying cabs.
    [13336] 140705.213958.3499: GenBmr: Applying "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\Amd64\WinPE_OCs\WinPE-Setup.cab".
    [13336] 140705.213959.9281: GenBmr: Customize WinPE failed: System.Management.Automation.CmdletInvocationException: The specified image file did not contain a resource section.
     ---> System.Runtime.InteropServices.COMException: The specified image file did not contain a resource section.
       at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
       --- End of inner exception stack trace ---
       at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
       at Microsoft.WindowsServerSolutions.PowerShell.PSRuntime.ExecuteCommandPrivate(String command, PSParameterList parameterList)
       at Microsoft.WindowsServerSolutions.PowerShell.PSRuntime.ExecuteCommand(String command, PSParameterList parameterList)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.ApplyCabsInternal(IEnumerable`1 cabsToApply, FilePathSubstituter substituter, String mountPath, PSRuntime psRunTime, Boolean multiLang)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.ApplyCabs(String mountPath, ImageKind imageKind, IEnumerable`1 serverLanguages)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.GenBmr.Tasks.CustomizeWinPETask.CustomizeImage(ImageKind imageKind)
    [13336] 140705.213959.9281: Task: In Task CustomizeWinPE: 
    [13336] 140705.213959.9281: TaskManagement: In TaskScheduler.ReportStatus(): Task("CustomizeWinPE") requested the engine stop processing Tasks!  Completed=True, Success=False
    [13336] 140705.213959.9281: GenBmr: Unmounting the image discarding changes.

  • In SM21 - Database error 235 at EXE

    Hello Gurus,
    In sm21 - Database error 235 at EXE this error shown in our test server, while investigating I found this
    ( I am attaching log for your reference )
    Details
    Recording at local and central time........................ 25.03.2009 23:02:24
    Task................ 15116  /  Background Processor No. 18
    User................ CSCADMIN_BC
    Client.............. 050
    Terminal............
    Session............. 1
    Transaction code....
    Program name........ RSORAHST
    Problem class....... K    SAP Web AS Problem
    Development class... SBAC
    Module name......... dbds
    Line................ 798
    Table name.......... 235
    Field name.......... EXE
    Documentation for system log message BY 2 :
    After the attempt to call a database operation, the database system has
    returned the error code specified in the message, which indicates that
    the operation concerned could not be executed successfully.
    Technical details
    File................ 018863
    Position............ 0000235620
    Entry type.......... h      ( Database Error (Non-SQL)       )
    Message ID.......... BY 2
    Variable parts...... 235       EXE                                       dbds    798
    The given program associated with this job SAP_PERIODIC_ORACLE_SNAPSHOT but this is run successfully on the test server.
    Can somebody tell me the error & the rectification for the same
    Thanks & regards
    Shishir

    Please check
    - ST22 for dumps
    - alert<SID>.log of the database
    - dev_w18 tracefile
    Do you use the same patches on both DEV and this system?
    Markus

  • Ipod Restore Error

    Hi all,
    Sorry to make my first post here a cry for help, but desperate times call for desperate measures.
    For the past day or 2, my iPod has been stuck on the loading screen (apple logo) when turned on, and it is not being picked up by iTunes. From reading other threads, I decided to put it into restore mode and reinstall the firmware.
    The problem arises now, during the restore, the iPod seems to leave restore mode and go back to the loading screen. Windows indicates that a usb device has disconnected.
    At this point the restore will fail with Error: 6, and in one occasion Error:13.
    I'm at my wits end with this one and cannot think of a solution thus far. Any help any of you can provide would be greatly appreciated.
    Using: Windows XP
    iTunes: 8.0.2.20
    Firmware: 1.2.1
    Cheers,
    Rodg3

    HERE IS MY ERROR LOG IF IT HELPS ANYONE:
    2008-11-24 17:55:32.296 iTunes.exe[4752:1708]: restore library built Oct 24 2008 13:46:43
    2008-11-24 17:55:32.296 iTunes.exe[4752:1708]: iTunes: iTunes 8.0.2.20
    2008-11-24 17:55:32.296 iTunes.exe[4752:1708]: iTunes: Software payload version: 5G77a
    2008-11-24 17:55:32.562 iTunes.exe[4752:e40]: AMDeviceIoControl: GetOverlappedResult failed
    2008-11-24 17:55:32.562 iTunes.exe[4752:e40]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
    2008-11-24 17:55:33.062 iTunes.exe[4752:e40]: AMDeviceIoControl: GetOverlappedResult failed
    2008-11-24 17:55:33.062 iTunes.exe[4752:e40]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
    2008-11-24 17:55:33.562 iTunes.exe[4752:e40]: AMDeviceIoControl: GetOverlappedResult failed
    2008-11-24 17:55:33.562 iTunes.exe[4752:e40]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
    2008-11-24 17:55:34.062 iTunes.exe[4752:e40]: USBControlTransfer: error 0, usbd status c0000004
    2008-11-24 17:55:34.062 iTunes.exe[4752:e40]: AMDeviceIoControl: GetOverlappedResult failed
    2008-11-24 17:55:34.062 iTunes.exe[4752:e40]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
    2008-11-24 17:55:34.562 iTunes.exe[4752:e40]: AMDeviceIoControl: GetOverlappedResult failed
    2008-11-24 17:55:34.562 iTunes.exe[4752:e40]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
    2008-11-24 17:55:35.062 iTunes.exe[4752:e40]: AMDeviceIoControl: GetOverlappedResult failed
    2008-11-24 17:55:35.062 iTunes.exe[4752:e40]: ProcessOverlappedIoRequest: failed, error 31, usbd status c0000004
    2008-11-24 17:55:35.562 iTunes.exe[4752:e40]: USBControlTransfer: error 0, usbd status c0000004
    2008-11-24 17:55:35.562 iTunes.exe[4752:e40]: radio-error not set
    2008-11-24 17:55:35.562 iTunes.exe[4752:e40]: unable to open device_map.txt: No such file or directory
    2008-11-24 17:55:35.562 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress -1
    2008-11-24 17:55:35.656 iTunes.exe[4752:e40]: bootstrapping restore with iBEC
    2008-11-24 17:55:35.656 iTunes.exe[4752:e40]: WinDFU::OpenDFUDevice: path: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#502e595d
    2008-11-24 17:55:35.656 iTunes.exe[4752:e40]: WinDFU::OpenDeviceByPath: \\?\USB#VID05AC&PID1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#502e595d
    2008-11-24 17:55:35.656 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 4
    2008-11-24 17:55:35.656 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 8
    2008-11-24 17:55:35.656 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 12
    2008-11-24 17:55:35.671 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 16
    2008-11-24 17:55:35.671 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 20
    2008-11-24 17:55:35.671 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 24
    2008-11-24 17:55:35.671 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 28
    2008-11-24 17:55:35.687 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 32
    2008-11-24 17:55:35.687 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 36
    2008-11-24 17:55:35.687 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 40
    2008-11-24 17:55:35.687 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 44
    2008-11-24 17:55:35.703 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 48
    2008-11-24 17:55:35.703 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 52
    2008-11-24 17:55:35.703 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 57
    2008-11-24 17:55:35.703 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 61
    2008-11-24 17:55:35.718 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 65
    2008-11-24 17:55:35.718 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 69
    2008-11-24 17:55:35.718 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 73
    2008-11-24 17:55:35.718 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 77
    2008-11-24 17:55:35.734 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 81
    2008-11-24 17:55:35.734 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 85
    2008-11-24 17:55:35.734 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 89
    2008-11-24 17:55:35.734 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 93
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 97
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: WinDFU::UploadData: EOF, cbRead: 2212
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 4 progress 100
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: WinDFU::UploadData: ZLP
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFESTSYNC
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: WinDFU::ProcessUpdateState: status.bState == DFUSTATEMANIFEST
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: WinDFU::ProcessUpdateState: status.bState == DFUSTATE_MANIFEST_WAITRESET
    2008-11-24 17:55:35.750 iTunes.exe[4752:e40]: WinDFU::ResetDevice: resetting...
    2008-11-24 17:55:36.140 iTunes.exe[4752:e40]: WinDFU::FinalizeDfuUpdate: success
    2008-11-24 17:55:36.140 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: operation 31 progress -1
    2008-11-24 17:55:37.140 iTunes.exe[4752:e40]: <Recovery Mode Device 01DC8D08>: Recovery mode succeeded
    2008-11-24 18:00:39.093 iTunes.exe[4752:1708]: iTunes: Restore error 1604

  • IPod restore error 1604

    iPod Touch 1.1.3 restore error in iTunes 7.6 -- Windows XP Pro
    I,ahem... JB'd... my iTouch, and I "DID NOT LIKE IT" so I tried restoring it. Now I get the error 1604 right after it is "Preparing iPod for restore..." screen, saying, "The iPod "iPod" could not be restored. An unknown error ocurred (1604)"
    I have looked on Apple.com and even Googled it for hours. I tried rebooting, trying another USB port, trying another user on the computer, and draining the iPod's batttery. Also, when it is restoring, the "Connect to iTunes screen" is still active and the white cord has the circle progress thingy. Is this normal? I have restored it before and it used to show the Apple logo with the circle thingy. Also, when I connect the iPod when it is booted to the "SpringBoard" iTunes says that "The iPod could not be synced because the Apple Mobile Device Service is not active" even after I located the "AppleMobileDeviceService.exe" and opened it. After the error message goes away when I click "OK" the iPod reboots into "DFU Mode" (as I think it is called). Also, I can only reboot it to the SpringBoard if I use Zibri's ZiPhone 2.0 utility to "Verbose Boot."

    For those of you who ask...
    JB is an acronym for JailBreak. I didn't want to spell it out directly in an Apple hosted Help Discussion, seeing as I don't want to deal with the consequences. If you still don't know what the above term means or refers to, go ahead and google it.
    DFU Mode: I suppose it stand for "Download Firmware Update" seeing as when I connect it during this mode that it has the error "Could not contact the iPod update server. Try again later" or something to that effect(my internet is not working, it is unrelated and the internet company is trying to solve the problem right now, but I am getting very impatient with them). I don't have any clue myself what it really stands for, and I can't find it anywhere on Apple.com. What exactly is DFU mode? I suppose it doesn't help even now, except for you to experience it for yourself:
    To get into "DFU Mode" hold down the home and power buttons until the iPod is shut off. At this point, keep holding the home button, but release the power button until iTunes detects it in that mode. The screen should remain black after it is shut off. If it reboots, or ends up in "Connect to iTunes Restore Mode" with a picture of the cable and iTunes logo, please try again.
    To get into restore mode with the iTunes logo and iPod cable, push AND hold the Home and power buttons until ou see the Apple logo. At the exact same moment you see the Apple logo, release the power button but keep holding the Home button until the above described screen is shown.
    My question: What is the difference between the two modes, and would DFU mode fix the 1604 error I receive when I try to restore it in "Connect to iTunes mode"?

  • Error Message: itunes.exe corrupt file

    Error Message: itunes.exe corrupt file
    \ipod_control\itunes\temp
    run chkdsk utility
    Itunes gives me this message, then acts normal
    downloads latest podcasts and videos but when I turn on the ipod video it hasn't been updated at all.
    Also from the start menu, I've tried to run chkdsk utility. when I do it does something 3-4 seconds and then that's it.
    My ipod shuffle works fine.
    Anybody have any ideas.
    Thanks

    try installing de software of that ipod, reinstall de ipod sofware and the itunes, after that go 2 apple.com and download the new updator. then install that too, and if possible redownload the new version of itunes. b4 u do all this , delete the software (old one ) of that ipod and itunes.. only the one that is giving u the problem, meaning b4 u reinstall the software that came with ur ipod, go 2 control panel.2.find add /remove programs.3then delete the old ipod and itunes software. then retstart ur computer. 4 then now go and reinstall the ipod software and itunes that came with ur ipod then after that redownload de ipod updator(new version is march 2006. get this and after that download the new version of itunes. then install all these, then u can also restore ur ipod by clicking on de updator when it opens press restore u will be commanded 2 plug in ur ipod. then follow de instructions. after all these ur itunes should be fine, and ur ipod software should be fine. ur itunes is corrupt , that might be causing the problem.

  • Windows failed to start. winload.exe corrupt

    Been having a few problems with my Equius so decided to boot, do F8, and do a toshiba system restore.
    Started up, and began formatting the disk. All of a sudden it blue screened.
    Trouble is now I cant even boot that far to get the recovery/restore option. I get :-
    Windows failed to start. A recent hardware or software change might be the
    cause. . .
    File: \Windows\system32\winload.exe
    Status:0xc000000f
    Info: The selected entry could not be loaded because the application is
    missing or corrupt.
    Not sure how it all works but I assume the recovery stuff is stored on a separate partition. Trouble is I guess you need to be able to start to load windows before you can even get to this?
    I've downloaded and tried a vista boot recovery disk with no joy, and of course, toshiba dont supply a vista disk. How on earth do I recover from this situation?

    Hello
    At first I must say that I cannot understand why you didnt write which Equium do you have exactly?
    Such info is always good for better understanding and discussion.
    So, if recovery media was not delivered I think you have newest notebook model. Recovery media is not delivered with new notebooks and it must be created using preinstalled "Toshiba Recovery Disc Creator". This software is preinstalled on all new Vista notebook. it can happen that people don't think about it and because of that Toshiba has designed small reminder with follow content:
    +*Important INFORMATION*+
    +*your system is equipped with hard disk recovery system. If you need to repair*+
    +*your computer by restoring it to original factory state, you can do it directly*+
    +*from harddisk (press F8 when you boot your computer, choose "Repair your computer"*+
    +*and follow the menue instructions) or create a bootable Recovery Disc Medium for this purpose.*+
    +*Toshiba recommends you to create Recovery Disc Medium using the "Toshiba Recovery Disc Creator"*+
    +*to ensure that you are able to restore your computer to the original factory installed state, even if your computer gets seriously damaged.*+
    So now the question: Have you seen this reminder? Have you ignored it? Have you started preinstalled OS at the first day?
    What you have done exactly?
    Sorry for all those questions but lot of people make big mistake: they don't even start preinstalled Vista and install WXP immediately.
    On this way you will not be able to create recovery DVD and you will also loose F8 option to install Vista from HDD.
    To be honest I don't know why this thread was posted under WXP category. As I wrote before after WXP installation on new notebooks you will not be able to use F8 and HDD recovery option.
    So if you want good answer please explain to us exactly which notebook model do you have and what you have done in the past.
    Bye my friend. Just stay cool we will find some solution or good explanation why this happen
    Have a nice day.

Maybe you are looking for