How to fix a system that won't start


  1. Posts : 7
    Win10
       #1

    How to fix a system that won't start


    Please healp me with this issue, I been 10hs trying to fix it, i would give up but i really need to make my system work.

    The problem is that my windows 10 went straight to the WinRE and i couldn't fix it, i tried all those bootrec comands, also mounting the EFI partition and recreating the BCD

    Nothing worked so installed another windows 10 alongside bc i needed to use the PC, this one works fine, but i really need my old windows back, something important is permanently lost if i can't run it again, this is what i tried on my working new installation:

    D: is the system of my old windows

    dism /image:D:\ /Cleanup-Image /RestoreHealth

    sfc /SCANNOW /OFFBOOTDIR=D:\ /OFFWINDIR=D:\windows

    The sfc /scannow gives OK, there is nothing to repair, i also loaded the boot files with:

    > bcdboot D:\windows
    Boot files successfully created


    Now when i try to boot my old windows it loads a blue screen that says

    your pc needs to be repaired
    file:\window\
    error:0xc000000d


    I don't know what else to do, i know the windows partition is okay, i suspect is something with the bootloader, at this point i don't know what else to do, i can't do a refresh because that option is not available.

    My "Real" Windows 10 version is the 10.0.18362.959
    The new one is the 10.0.19041.264

    StrTrail.txt


    Startup Repair diagnosis and repair log
    ---------------------------
    Last successful boot time: ‎7/‎18/‎2020 5:07:00 AM (GMT)
    Number of repair attempts: 5


    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = C:\Windows
    AutoChk Run = 0
    Number of root causes = 1


    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 15 ms


    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 141 ms


    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code = 0x0
    Time taken = 31 ms


    Test Performed:
    ---------------------------
    Name: Volume content check
    Result: Completed successfully. Error code = 0x0
    Time taken = 63 ms


    Test Performed:
    ---------------------------
    Name: Boot manager diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: System boot log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Event log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 31 ms


    Test Performed:
    ---------------------------
    Name: Internal state check
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Check for installed LCU
    Result: Completed successfully. Error code = 0x0
    Time taken = 4969 ms


    Test Performed:
    ---------------------------
    Name: Check for installed driver updates
    Result: Completed successfully. Error code = 0x0
    Time taken = 1453 ms


    Test Performed:
    ---------------------------
    Name: Check for pending package install
    Result: Completed successfully. Error code = 0x0
    Time taken = 3718 ms


    Test Performed:
    ---------------------------
    Name: Boot status test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Setup state check
    Result: Completed successfully. Error code = 0x0
    Time taken = 157 ms


    Test Performed:
    ---------------------------
    Name: Registry hives test
    Result: Completed successfully. Error code = 0x0
    Time taken = 968 ms


    Test Performed:
    ---------------------------
    Name: Windows boot log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Root cause found:
    ---------------------------
    Boot critical file c:\windows\ is corrupt.


    Repair action: File repair
    Result: Failed. Error code = 0x57
    Time taken = 2000 ms


    Repair action: System files integrity check and repair
    Result: Failed. Error code = 0x57
    Time taken = 1360 ms


    ---------------------------
    ---------------------------
    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = C:\windows
    AutoChk Run = 0
    Number of root causes = 1


    Test Performed:
    ---------------------------
    Name: Buscar actualizaciones
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Prueba de disco del sistema
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Diagnóstico de errores de disco
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Prueba de metadatos de disco
    Result: Completed successfully. Error code = 0x0
    Time taken = 125 ms


    Test Performed:
    ---------------------------
    Name: Prueba de metadatos de disco
    Result: Completed successfully. Error code = 0x0
    Time taken = 16 ms


    Test Performed:
    ---------------------------
    Name: Prueba de sistema operativo de destino
    Result: Completed successfully. Error code = 0x0
    Time taken = 15 ms


    Test Performed:
    ---------------------------
    Name: Comprobación de contenido de volumen
    Result: Completed successfully. Error code = 0x0
    Time taken = 63 ms


    Test Performed:
    ---------------------------
    Name: Diagnóstico del administrador de arranque
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Diagnóstico de registro de arranque del sistema
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Diagnóstico de registro de eventos
    Result: Completed successfully. Error code = 0x0
    Time taken = 16 ms


    Test Performed:
    ---------------------------
    Name: Comprobación de estado interno
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Buscar LCU instalado
    Result: Completed successfully. Error code = 0x0
    Time taken = 3703 ms


    Root cause found:
    ---------------------------
    A recently serviced boot binary is corrupt.


    ---------------------------
    ---------------------------
    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = C:\Windows
    AutoChk Run = 0
    Number of root causes = 1


    Test Performed:
    ---------------------------
    Name: Buscar actualizaciones
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Prueba de disco del sistema
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Diagnóstico de errores de disco
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Prueba de metadatos de disco
    Result: Completed successfully. Error code = 0x0
    Time taken = 141 ms


    Test Performed:
    ---------------------------
    Name: Prueba de metadatos de disco
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Prueba de sistema operativo de destino
    Result: Completed successfully. Error code = 0x0
    Time taken = 15 ms


    Test Performed:
    ---------------------------
    Name: Comprobación de contenido de volumen
    Result: Completed successfully. Error code = 0x0
    Time taken = 63 ms


    Test Performed:
    ---------------------------
    Name: Diagnóstico del administrador de arranque
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Diagnóstico de registro de arranque del sistema
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Diagnóstico de registro de eventos
    Result: Completed successfully. Error code = 0x0
    Time taken = 31 ms


    Test Performed:
    ---------------------------
    Name: Comprobación de estado interno
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms


    Test Performed:
    ---------------------------
    Name: Buscar LCU instalado
    Result: Completed successfully. Error code = 0x0
    Time taken = 3734 ms


    Root cause found:
    ---------------------------
    A recently serviced boot binary is corrupt.


    Repair action: Uninstall latest LCU
    Result: Failed. Error code = 0x825
    Time taken = 2453 ms


    ---------------------------
    ---------------------------

      My Computer


  2. Posts : 35,557
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #2

    Have you checked your disk? E.g. boot from a live boot disk such as Kyhi's or Bob Omb's (Google) and run HD Tune Health and Error scan tabs?

    I hope you have noted the so, so often given advice here to use disk imaging routinely.

    If so, and your disk has not failed, then all you have to do is to restore a recent disk image of your Windows partitions. E.g. Macrium reflect - free/paid- + external storage for disk image files.

    Please boot from a live boot disk and post a screenshot of your partitions.

    You can try creating Macrium Reflect's boot disk, or e.g. Kyhi's boot disk with Macrium Reflect on it, and use the Fix boot utility provided by Macrium Reflect.

    If you were to boot your PC from a Win 10 bootable disk, and click on Repair your computer, you could try Startup Repair, but Macrium Reflect's Fix boot seems to be more comprehensive.

    Either way, if you try those,report what they say.
      My Computers


  3. Posts : 7
    Win10
    Thread Starter
       #3

    I runned chkdsk everything was OK

    I'm on a fresh windows installation, these are my partitions:

    How to fix a system that won't start-yy.png

    - - - Updated - - -

    dalchina said:
    Fix boot utility provided by Macrium Reflect.
    I just tried that with the macrium reflect rescue iso, the two systems bcd were rebuilt by the tool, but when i enter my old system is still the blue screen.
      My Computer


  4. Posts : 35,557
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #4

    If you have 2 Windows partitions, could be Fix Boot would be confused. At the least you should hide the broken windows partition, then try a repair.

    Given you have that, how did you subsequently install Windows? To install Windows requires you delete ALL existing Windows O/S partitions.

    More information is shown if you use a 3rd party partition manager from a live boot disk.

    + need a disk test.
      My Computers


  5. Posts : 7
    Win10
    Thread Starter
       #5

    Given this results, does that mean my system is OK and recoverable? the problem is with the boot?



    Microsoft Windows [Version 10.0.19041.264]
    (c) 2020 Microsoft Corporation. All rights reserved.


    C:\WINDOWS\system32>dism /image:D:\ /Cleanup-Image /RestoreHealth


    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1


    Image Version: 10.0.18363.959


    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.



    C:\WINDOWS\system32>sfc /SCANNOW /OFFBOOTDIR=D:\ /OFFWINDIR=D:\windows


    Beginning system scan. This process will take some time.




    Windows Resource Protection did not find any integrity violations.


    C:\WINDOWS\system32>chkdsk D: /f
    The type of the file system is NTFS.


    Chkdsk cannot run because the volume is in use by another
    process. Chkdsk may run if this volume is dismounted first.
    ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
    Would you like to force a dismount on this volume? (Y/N) y
    Volume dismounted. All opened handles to this volume are now invalid.


    Stage 1: Examining basic file system structure ...
    1094144 file records processed.
    File verification completed.
    Phase duration (File record verification): 4.47 minutes.
    7550 large file records processed.
    Phase duration (Orphan file record recovery): 0.00 milliseconds.
    0 bad file records processed.
    Phase duration (Bad file record checking): 1.60 milliseconds.


    Stage 2: Examining file name linkage ...
    3195 reparse records processed.
    1363914 index entries processed.
    Index verification completed.
    Phase duration (Index verification): 39.59 seconds.
    0 unindexed files scanned.
    Phase duration (Orphan reconnection): 10.03 seconds.
    0 unindexed files recovered to lost and found.
    Phase duration (Orphan recovery to lost and found): 4.52 milliseconds.
    3195 reparse records processed.
    Phase duration (Reparse point and Object ID verification): 22.67 milliseconds.


    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 98.82 milliseconds.
    134886 data files processed.
    Phase duration (Data attribute verification): 0.56 milliseconds.
    CHKDSK is verifying Usn Journal...
    34712432 USN bytes processed.
    Usn Journal verification completed.
    Phase duration (USN journal verification): 218.61 milliseconds.


    Windows has scanned the file system and found no problems.
    No further action is required.


    165169675 KB total disk space.
    119501816 KB in 738088 files.
    377500 KB in 134887 indexes.
    0 KB in bad sectors.
    1206503 KB in use by the system.
    65536 KB occupied by the log file.
    44083856 KB available on disk.


    4096 bytes in each allocation unit.
    41292418 total allocation units on disk.
    11020964 allocation units available on disk.
    Total duration: 5.30 minutes (318384 ms).


      My Computer


  6. Posts : 35,557
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #6

    Running checks purely on your Windows partition only verifies that, and tells you nothing about other things that are necessary for your PC to boot.

    Noted no response to my previous. I'll wish you good luck and leave you with this method if all else fails:

    Create a disk image of C:
    Clean install Win 10 deleting existing partitions.
    Restore your image of C: in place of the newly created Windows partition.
    Restart- either automatic repair will kick in, or you can run Startup Repair.
      My Computers


  7. Posts : 7
    Win10
    Thread Starter
       #7

    dalchina said:
    Running checks purely on your Windows partition only verifies that, and tells you nothing about other things that are necessary for your PC to boot.
    I know my thread is a mess, i'll try to explain the best i can

    My windows broke when i used a Clover Mojave ISO in a USB stick and it was stuck loading something so i shut down the PC with the power button (it was dumb but i didn't know how to exit). Then my windows would go directly to the automatic repair and failed.

    After that i tried repairing the boot files with all the bootrec commands (fixmbr, fixboot, scanos, buildbcd), mounting the efi partition and doing the bootrec commands in there, deleting the EFI partition and manually creating it again, and other stuff i don't remember, nothing works. The system itself (the windows partition) seems to be perfect but for some reason i can't boot it, i'm not lying when i say i am +10hs working on this

    I need my original system and not just copy my files to the new installation because i was using Chrome Portable with an open session in a website which i have no way of accessing now, and is very important to me to at least access one more time ( Google Chrome specifically locks your password store to a specific Windows install whether run locally or portably )

    Given that my windows partition seems to be OK, do you think there is hope to be able to boot it?

    I passed the HD Tune program but nothing seems wrong

    How to fix a system that won't start-kkk.pngHow to fix a system that won't start-hhh.png

    These are the commands that i ran from the fresh install to check and repair my windows (the original, in D:).


    > dism /image:D:\ /Cleanup-Image /RestoreHealth

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    > sfc /SCANNOW /OFFBOOTDIR=D:\ /OFFWINDIR=D:\windows

    Windows Resource Protection did not find any integrity violations.

    > chkdsk D: /f

    0 KB in bad sectors.


    - - - Updated - - -

    Here is an image of the partitions in Disk Managment

    How to fix a system that won't start-bbb.png

    What i see is that the clean installation has the labels Boot, PageFile, Crash Dump but my windows only has Basic Data Partition
    Last edited by SVai; 19 Jul 2020 at 11:31.
      My Computer


  8. Posts : 35,557
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #8

    Thanks. Given the complicated history the approach I'd take is as per my previous post:

    Create a disk image of your Windows partition: (e.g. using Macrium reflect -> external storage).
    Clean install Win 10 deleting existing partitions, using a bootable disk of the same major build number.
    Check that boots ok. Nothing more.
    Restore your image of the Windows partition: in place of the newly created Windows partition.
    Restart- either automatic repair will kick in, or you can run Startup Repair.

    All builds of Win 10 are freely downloadable. See tutorial on downloading a Win 10 iso to get one for your build.
    If you already have a bootable disk of the same build, you can use that.
      My Computers


  9. Posts : 7
    Win10
    Thread Starter
       #9

    dalchina said:
    Thanks. Given the complicated history the approach I'd take is as per my previous post:

    Create a disk image of your Windows partition: (e.g. using Macrium reflect -> external storage).
    Clean install Win 10 deleting existing partitions, using a bootable disk of the same major build number.
    Check that boots ok. Nothing more.
    Restore your image of the Windows partition: in place of the newly created Windows partition.
    Restart- either automatic repair will kick in, or you can run Startup Repair.

    All builds of Win 10 are freely downloadable. See tutorial on downloading a Win 10 iso to get one for your build.
    If you already have a bootable disk of the same build, you can use that.
    It also boots to the blue screen. I was lucky enough i could access my account so i don't need to solve this anymore , but i appreciate your help.
      My Computer


  10. Posts : 35,557
    Win 10 Pro (21H2) (2nd PC is 21H2)
       #10

    From that I don't know what boots to a blue screen at which stage, but I would guess either you haven't created the bootable disk correctly, or not really booted your system from it, or not truly clean installed.

    It's a sequence of steps you need to take correctly.

    If you had clean installed Win 10 and the hardware was ok, hopefully there wouldn't have been a BSOD.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:23.
Find Us




Windows 10 Forums