Endless reboots following update installation

Page 3 of 3 FirstFirst 123

  1. Posts : 180
    Windows 10 Professional
    Thread Starter
       #21

    OK. I installed 18363.657. Worked flawlessly. I installed 18363.693 and it did several reboots and came up with blue windows screen stating it previously did not boot correctly and what do you want to do. I told it to continue and load Windows.

    It booted OK this time. Once I saw that it was stable I tried another reboot and it was OK. It has been running 15 minutes and counting.

    I just checked build number. It did not change. It is still 18363.657, so the 693 update did not take.

    I retried installing 18363.693 and now it is continually rebooting. Dead in the water.
      My Computers


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

    I suggest you have two basic options.

    1. To continue using your PC, the best you can do is to update to 18363.657, then use e.g. Sledgehammer (free) to block Windows updates; that allows Defender to continue updating and provides you with the means to perform a manual scan for updates.

    You could also consider using the tool in Option 7 of the tutorial on disabling automatic updates.

    2. Other than that, since you get a BSOD, you can refer this to the BSOD section for analysis. Posting there requires you to use a tool to upload data for the members who try to help there.

    More:
    How old is your PC? Is the BIOS fully up to date?

    Are you over-clocking?

    KB4535996 CU Win 10 v1903 build 18362.693 and v1909 build 18363.693
    - addresses many many issues including at least one BSOD. Have a careful look through the list and see if anything there rings bells.

    I don't know if you followed this
    Before installing this update

    Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

    If you are using Windows Update, the latest SSU (KB4538674) will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.
    - but it probably isn't relevant give earlier failures via Windows Update.
      My Computers


  3. Posts : 180
    Windows 10 Professional
    Thread Starter
       #23

    dalchina said:
    I suggest you have two basic options.
    2. Other than that, since you get a BSOD, you can refer this to the BSOD section for analysis. Posting there requires you to use a tool to upload data for the members who try to help there.
    I was afraid of that when I wrote it. I do not get the traditional BSOD as I am familiar with from my Win7 days. You know blue scary screen tons of text . This one is simple. States it did not boot correctly last time. Want to try repair or continue on to Windows.
      My Computers


  4. Posts : 1,806
    Windows 10 Pro 21H1 19043.1348
       #24

    Hi Stephen, why not clean install 1909 and Sledgehammer or Matthew Wai's fix?

    The end of service on 1909 is May 11, 2021 and hopefully by that date more of the bugs will be worked out of 2004. This could potentially solve your grief or at least by that date, we may have learned the solution for your particular challenge.
      My Computer


  5. Posts : 180
    Windows 10 Professional
    Thread Starter
       #25

    W10 Tweaker said:
    Hi Stephen, why not clean install 1909 and Sledgehammer or Matthew Wai's fix?

    The end of service on 1909 is May 11, 2021 and hopefully by that date more of the bugs will be worked out of 2004. This could potentially solve your grief or at least by that date, we may have learned the solution for your particular challenge.
    I don't mind doing that. I really don't use the computer at all except to periodically start it up to receive updates. I would not even need the stopping of updates. I could just leave it in the closet until after EOS for 1909.

    I guess I am worried there is something wrong with the computer. It never had issues until the updates.


    What I do not understand is what will happen after the EOS for 1909. I always thought I had to install ALL updates in sequence.
      My Computers


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

    What I do not understand is what will happen after the EOS for 1909.
    - you will receive no more routine updates for 1909.

    If you take no other action, you may (and this is untested) receive an automatic upgrade to 2004.


    I always thought I had to install ALL updates in sequence.
    Not true. As I think I said, normal Windows Updates are cumulative. E.g. skip 5, and the 6th covers all.

    Also not true as regards feature upgrades. E.g. I'm on 1903, and could go to 2004 directly.
      My Computers


  7. Posts : 180
    Windows 10 Professional
    Thread Starter
       #27

    OK. I think I get it. I will put it back to 18363.657 and store it in the closet until 1909 is retired and then try again.

    Thanks for your help. I may be looking you up next Spring. Fingers crossed.
      My Computers


  8. Posts : 1,806
    Windows 10 Pro 21H1 19043.1348
       #28

    SJMaye said:
    I don't mind doing that. I really don't use the computer at all except to periodically start it up to receive updates. I would not even need the stopping of updates. I could just leave it in the closet until after EOS for 1909.
    I guess I am worried there is something wrong with the computer. It never had issues until the updates.

    How old is the PC? More than likely the problem is related to a particular part of that OS build (2004) isn't compatible with a hardware device and/or drivers for that device. In the past, we've often seen staged deployment of a new OS that is specifically driven by compatibility with users devices but MS can't always get that delivery perfect for every device.


    This MSI laptop I'm using is the perfect example. It was new to me in October 2018 and a bit less than current at the time. Whenever a new OS arrived, it wasn't offered to me immediately and I was aware of various incompatibilities relating to GPU drivers etc. Within a couple of months the problems were sorted out by MS and Nvidia. The OS was then offered without any actions required on my part.


    SJMaye said:
    What I do not understand is what will happen after the EOS for 1909. I always thought I had to install ALL updates in sequence.

    I'm still using 1809 because it works very well for my use. I plan to clean install 1909 sometime in the next month because I'd prefer to avoid 2004 until more bugs are worked out. I understand 2004 may function just great for a large percentage of users but if it isn't perfect, why bother?

    I spend enough time tweaking to perfect the function of this PC, I'd prefer to not cut in to my fun time with struggling for basic functionality because of significant compatibility issues.

    I try to complete my OS installations at least 30 days before the EOS date as I have 3 laptops to update and that allows sufficient time if other distractions delay the PC work.
      My Computer


  9. Posts : 180
    Windows 10 Professional
    Thread Starter
       #29

    The computer is a Acer Veriton VN4620G-i5333X built in 2014. It is a small form factor like the chromeboxes that mount to the back of a monitor, but this has an i5 CPU and 8GB of ram. Still pretty zippy, so I want to hold on to it.

    If come May 2021 I still have this problem maybe I will convert it to a ChromeOS or Linux.
      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 12:04.
Find Us




Windows 10 Forums