Windows 10: Windows 10 crashed after update and is now unbootable Solved

Page 3 of 4 FirstFirst 1234 LastLast
  1.    2 Weeks Ago #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 ComputerSystem Spec


  2. Posts : 20,976
    windows 10 professional version 1607 build 14393.969 64 bit
       2 Weeks Ago #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 ComputerSystem Spec

  3.    2 Weeks Ago #23

    zbook said: View Post
    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: View Post
    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 ComputerSystem Spec


  4. Posts : 20,976
    windows 10 professional version 1607 build 14393.969 64 bit
       2 Weeks Ago #24

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

  5. Bree's Avatar
    Posts : 8,850
    10 Home x64 (1809) (10 Pro on 2nd pc)
       2 Weeks Ago #25

    dalchina said: View Post
    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.

    Click image for larger version. 

Name:	RegBack 1.PNG 
Views:	1 
Size:	22.9 KB 
ID:	207349

    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'.

    Click image for larger version. 

Name:	RegBack task triggers 1.PNG 
Views:	1 
Size:	16.8 KB 
ID:	207350

    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.


    Click image for larger version. 

Name:	RegBack after restart.PNG 
Views:	1 
Size:	32.2 KB 
ID:	207351



    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.

    Click image for larger version. 

Name:	RegBack 2.PNG 
Views:	1 
Size:	54.6 KB 
ID:	207361

    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.

    Click image for larger version. 

Name:	RegBack 2 after restart.PNG 
Views:	1 
Size:	41.5 KB 
ID:	207367
    Last edited by Bree; 2 Weeks Ago at 06:00. Reason: Second test
      My ComputersSystem Spec

  6.    2 Weeks Ago #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; 2 Weeks Ago at 07:11.
      My ComputerSystem Spec

  7. Bree's Avatar
    Posts : 8,850
    10 Home x64 (1809) (10 Pro on 2nd pc)
       2 Weeks Ago #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 ComputersSystem Spec

  8. Bree's Avatar
    Posts : 8,850
    10 Home x64 (1809) (10 Pro on 2nd pc)
       1 Week Ago #28

    Bree said: View Post
    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.

    Click image for larger version. 

Name:	RegBack after 24 hours.PNG 
Views:	2 
Size:	4.8 KB 
ID:	207672
      My ComputersSystem Spec

  9. Bree's Avatar
    Posts : 8,850
    10 Home x64 (1809) (10 Pro on 2nd pc)
       1 Week Ago #29

    Bree said: View Post
    ...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 ComputersSystem Spec

  10.    1 Week Ago #30

    Thanks. Found this curious:
    Click image for larger version. 

Name:	1.jpg 
Views:	2 
Size:	54.1 KB 
ID:	207749
    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 ComputerSystem Spec


 
Page 3 of 4 FirstFirst 1234 LastLast

Related Threads
Solved windows 10 update crashed computer in Windows Updates and Activation
My windows 10 was driving me crazy trying & failing to update. I tried to stop auto update , but couldn't. Finally I went to Microsoft and downloaded the correct update. It downloaded for a long time and when activated later, it updated for over an...
9/1/2016 update rendered my machine unbootable . . . in Windows Updates and Activation
-Don't know what number update this was that I automatically received yesterday, but it left my current configuration unbootable, so that even my Macrium Reflect "Fix Boot Errors" could not fix it . . . -Ran my last Full Backup from Reflect's...
Anniversary update fails, leaving system unbootable in Windows Updates and Activation
Perhaps someone can tell me what went wrong here. I have a bottom-rung Dell Inspiron 330s that I inherited from a family member. It shipped with Win7 Home, and while it was eligible I had updated it to Win10 1511. Very little if anything on it...
Solved Windows 10 update crashed OS in General Support
Hi. I am having a question and I hope I could get some help here. The issue is that I have installed windows 10 (just as anyone else) on 29th July and it worked smoothly, fast and robustly. Really, no abjection whatsoever. Then, yesterday, I had an...
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:26.
Find Us