Windows 10 crashed after update and is now unbootable

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 66
    Windows 10 Pro 1809 x64
    Thread Starter
       #21

    AFAIK September 29 I was working on the machine. I updated the BIOS, installed a new CPU and 1tb hard drive, and imaged over the installation from the original, tired ten-year-old hard drive. There was some file system corruption present on the 29th, which I fixed with a chkdsk. In addition, the old hard drive has one (and only one) bad sector.

    It makes sense that today there was an issue with the Registry. After all, it was copying over older versions of the Registry files that salvaged this installation. The first boot after the copy took a long time. The system restore also took a long time, but ultimately completed successfully.

    The most interesting thing is that RemotelyAnywhere (LogMeIn) is installed on this machine and is causing problems. I'm told this is used for remote support for the client management system installed.

    The crash that corrupted the Registry occurred on October 3rd. I don't see anything from that date.
      My Computer


  2. Posts : 39,955
    windows 10 professional version 1607 build 14393.969 64 bit
       #22

    There were no log entries between October 3 and October 6.
    This may relate to the date of the registry backup.

    The logs had a registry hive corruption entry on October 6, 2018.
      My Computer


  3. Posts : 66
    Windows 10 Pro 1809 x64
    Thread Starter
       #23

    zbook said:
    There were no log entries between October 3 and October 6.
    This may relate to the date of the registry backup.
    Yes. The installation was unbootable from the 3rd to until the evening of the 6th.

    zbook said:
    The logs had a registry hive corruption entry on October 6, 2018.
    That occurred when the machine booted for the first time with the copied-in Registry files. I noticed Windows was struggling to boot.

    I found filesystem corruption after the old drive was imaged to the new, but repaired it. That was on September 29th. And, I uninstalled RemotelyAnywhere; it had been installed two years ago, under Vista.

    Meanwhile, the repaired install has been imaged and the machine will be returning to service today.
      My Computer


  4. Posts : 39,955
    windows 10 professional version 1607 build 14393.969 64 bit
       #24

    When available please update the thread with the results of steps in post #20.
      My Computer


  5. Posts : 24,545
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #25

    dalchina said:
    Bree noted the default last run date for a new 1809 installation was 1999... perhaps indicating when it was introduced first. I have wondered if it's a relic of 'Last Known Good Configuration'.
    @dalchina has asked me to test setting a trigger at startup for RegIdleBack in 1803. Here are the results.

    This machine had a clean install of x64 1803 on 19 Sept 2018. Before I started the test the System32\config\RegBack folder contained zero-length files dated three months before the time on the clean install (I didn't even own the machine then).
    Edit: In the light of day I have double checked my receipts and seems I got two machines mixed up. The clean install would have been on 19th June 2018 after all.

    Windows 10 crashed after update and is now unbootable-regback-1.png

    AlthoughTask Scheduler showed a blank 'Triggers' column, on opening the task to add a trigger there was already a 'One time' trigger set for 21.45 today which had not yet run at 22:20 when I opened Task Scheduler to check. It did however show a Last Run Time dated 6th Oct and a Last Run Result of (0x0) indicating success, which is odd as the file dates on the files were still showing the earlier date. I then added the trigger for 'At startup'.

    Windows 10 crashed after update and is now unbootable-regback-task-triggers-1.png

    Shutting down then staring up did not immediately run the task, but after leaving it idle for about ten minutes the task now shows a Last Run Time of 7th Oct 2018 at 22:31 and a Last Run Result of (0x0). However the files in RegBack are still zero length and dated 19th July. Basically, it appears this task doesn't do the work it is supposed to do.


    Windows 10 crashed after update and is now unbootable-regback-after-restart.png



    A second test on my x86 test machine (System Two below) after restoring its 1803 17134.320 image.

    Initially Task scheduler showed no triggers at all, a Last Run Time of 3rd Oct 2018 and zero-length files in RegBack dated 3rd May 2018.

    Windows 10 crashed after update and is now unbootable-regback-2.png

    After setting a trigger for 'At startup', restarting and leaving idle about 20 minutes later the task ran. None of the files in RegBack changed, they were still zero-length and dated 3rd May.

    Windows 10 crashed after update and is now unbootable-regback-2-after-restart.png
    Last edited by Bree; 08 Oct 2018 at 06:00. Reason: Second test
      My Computers


  6. Posts : 34,896
    Win 10 Pro (1903) (2nd PC is 21H2)
       #26

    @Bree- thanks. One remaining possibility which I observed is that the action (I suspect) will only run and update the backup files on the first restart of a day. That is, mine are updated each day, having added the trigger, but if I restart later that day, are not updated again.

    Noted this morning that the task had not run after 2 restarts > 24 hrs after yesterday's.
    However, manually running for the first time today worked. (Whereas having been run that day it hadn't previously had any effect).

    Another is that it still works in 1709, but is somehow not effective in later builds.
    Last edited by dalchina; 08 Oct 2018 at 07:11.
      My Computers


  7. Posts : 24,545
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #27

    These are laptops, so I usually hibernate them rather than shut down. I'll shut down the x86 test machine and report back in 24+ hours.
      My Computers


  8. Posts : 24,545
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #28

    Bree said:
    I'll shut down the x86 test machine and report back in 24+ hours.
    @dalchina, some 36 hours later I started up the test machine. Even after leaving it idle for a couple of hours the RegIdleBack task has not run. It still shows the same Last Run Time as it had when I shut it down. I'll leave it idle over night to see if it ever runs.

    Windows 10 crashed after update and is now unbootable-regback-after-24-hours.png
      My Computers


  9. Posts : 24,545
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #29

    Bree said:
    ...I'll leave it idle over night to see if it ever runs.
    No. Some 12 hour later it still hasn't run. I'll try a Restart and leave it for a few more hours...
      My Computers


  10. Posts : 34,896
    Win 10 Pro (1903) (2nd PC is 21H2)
       #30

    Thanks. Found this curious:
    Windows 10 crashed after update and is now unbootable-1.jpg
    Note the time.

    I first booted up from cold early this morning.
    I did a restart at lunchtime- pending update.

    The task seems to have run on the 2nd event.

    I had one other occurrence of it not running on the morning boot, and after that I could run it manually.

    I'm still wondering if this is disabled from build 1803...
      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 19:18.
Find Us




Windows 10 Forums