• Rollback to 21H2 from 22H2

    Home » Forums » AskWoody support » Windows » Windows 10 » Windows 10 version 22H2 » Rollback to 21H2 from 22H2

    Author
    Topic
    #2503817

    I followed Susan’s rec and update my Windows 10 Pro to 22H2. Since then, file explorer is glitchy, my gigabyte video card control software will not run and Firefox is very slow.

    I mistakenly did not do a full backup before updating.

    Is there a way that I can roll back to 21H2.

     

    Thank you

    Viewing 3 reply threads
    Author
    Replies
    • #2503821

      Settings, Update & Security, Recovery, Go back to the previous version of Windows 10, Get started:

      How to Uninstall/Go back/Downgrade Win 10 22H2 to 21H2 or Earlier [MiniTool Tips]

      Windows 11 Pro version 22H2 build 22621.1192 + Microsoft 365/Edge

      • #2503822

        Thank you, but that does not work. Even though I did the update yesterday, Windows says that it happened more than 10 days ago and the option to roll back is greyed out.

        • #2503898

          give me a screen shot as rolling back should work.  Unless I’ve time travelled, it’s only been a day.

          That said I’d start with your video card driver.  Ensure you are on the latest not beta/ but fully supported version of the video card driver.

          Susan Bradley Patch Lady

          • #2503920

            Here is the screenshot of the greyed out option, Susan.

            I took your advice and looked for new drivers. Coincidentally, Nvidia issued new drivers for my hold 1050 card on December 1 – 5 days ago. I’ve just installed them and report back as soon as I’ve put my PC through its paces.

            Attachments:
            • #2504017

              By any chance do you have any other hard drive clean up routine?  As there’s no way it’s been 10 days.  The only reason why that should look like that would be if something or some routine has cleared out the windows.old file.

              Susan Bradley Patch Lady

            • #2504125

              I have found some things that are interesting – at least to me.  🙂

              1. I updated 2 desktops from 21H2 to 22H2. On one, I was not offered the update in the usual update process, so I followed Susan’s advice and went onto the MS site and updated from there. That seemed to go well. The “interesting” part is that there is a windows.old folder on that PC. Further, the option to roll back is active and not greyed out. Call that one PC1.
              2. The second PC is the one that I wrote about – PC2. The update on that one was offered in windows update and I chose it. That’s when the stuff hit the fan. It did the update, but caused many issues.
              3. I followed Susan’s advice and found graphics drivers that are only 5 days old on the nvidia site. I installed them last night and all the issues that I had on this PC2 seem to have been resolved. Fingers crossed.  thank you, Susan.
              4. On PC1, the update seems to have changed the sharing settings for files. I was not able to access shared drives from PC2. I had go in and change the sharing settings back to where they were. Then, all was well.
              5. On PC2, one of the things that seem to have happened with the update was that the Gigabyte/Aorus software that I use to control the fans on my Gigabyte/Nvidia graphics card was no longer starting with windows. As a result, the card got too hot and shut down the PC – twice. It took me that long to figure out what had happened and to fix it. It seems good now.
              6. The file explorer issue, where it did not refresh following actions like folder renaming and file deletion, seems to have been fixed by the new graphic drivers.  Once again, thank you Susan.

              So, it would seem all is well now. Oh, to reply, Susan, I don’t use any disk cleaning apps that would have deleted windows.old. I do use CCleaner, but I use it on both PC1 and PC2. I’ve never known it to deleted windows.old on either of them using its default settings. I’m open to you telling me that I am mistaken, though. To confirm my understanding of that, I just ran CCleaner on PC1, and windows.old is still there after the standard cleaning.

              Thanks much to everyone who joined in to help me.

              2 users thanked author for this post.
            • #2504287

              Yesterday afternoon I used your registry key to change 21H2 to allow and stay at 22H2. Windows did not update on its own and I was going to just wait but then this evening I found this link here and used it. https://catalog.s.download.windowsupdate.com/c/upgr/2022/07/windows10.0-kb5015684-x64_523c039b86ca98f2d818c4e6706e2cc94b634c4a.msu

              I now have Windows 10 22H2 as of 5:30pm.

              This evening at 6:00pm I also downloaded your registry key to extend roll back period to 60  days.

              I am having no problems but something has gone sideways with recovery. I searched for windows.old file on my C drive to see if it was there and it was not found.

              So I went to settings and Recovery reports PC updated more than 10 days ago, see attachment, but it hasn’t even been 10 hours.

              I have no idea what happened.

              HP Pavilion Desktop TP01-0050 – 64 bit
              Windows 10 Home Version 22H2
              OS build 19045.2486
              Windows Defender and Windows Firewall
              Microsoft Office Home and Business 2019
              -Version 2211(Build 15831.20208 C2R)

              Attachments:
    • #2503827

      You might see it in the old Programs and Features, View installed updates. KB5015684.

    • #2503864

      So that means that 22H2 is not safe to install !

      • #2503865

        What about the November 21H1 update ? Still at defcon 3 ?

        • #2503876

          Remember that due to differences in hardware, software installed, and drivers that everyone’s computer is unique – problems that one user, or even 100, have are almost guaranteed not to happen to you.  The opposite is also true – just because hundreds of users have no problem, does not mean a user is to blame for their problems or they are not real.  But determining the cause of problems, lets just say is difficult.  Better, when they appear, is to focus on the solutions.   One solution, if you have planned ahead, is to restore from a backup.

      • #2503877

        I cannot say that. I had 21H2 running fine for a long time. I held off on 22H2 until Susan said that it was a good this past week. In my case, it has caused problems. Clearly, that was Susan’s experience and it may not be yours. All I know for sure is that I have a bit of a mess on my hands and the usual way of rolling  back does not work. I have not yet had time to follow the other advice that I have received here. I plan to do that this evening, following a full backup.

        • #2503897

          I just gave the go-ahead on Monday, it’s not been 10 days.

          Susan Bradley Patch Lady

      • #2503910

        One person’s experience doesn’t mean that it’s not safe for all.

        Ensure your video card driver is up to date.

        Susan Bradley Patch Lady

        • #2503915

          Thanks for taking the time to get in on this, Susan. I now see that I mis-typed my reply. I meant to say that it was “not” your experience that the update was problematic. I apologize for causing confusion. I wanted to say that just because I am having issues does not mean everyone will. As I said, I only updated yesterday, so why windows thinks it’s been more than 10 days is beyond me. I will go onto the nvidia site to check for new drivers. It’s not been too long since I installed the current ones, but who knows?

           

          thanks again

    • #2504043

      By any chance do you have any other hard drive clean up routine?  As there’s no way it’s been 10 days.  The only reason why that should look like that would be if something or some routine has cleared out the windows.old file.

      Would it be the case that there’s no Windows.old because the enablement package was used? It wouldn’t be a full upgrade. As I mentioned above, I’d check Programs and Features > View installed updates and see if it’s there.

      • #2504141

        Would it be the case that there’s no Windows.old because the enablement package was used?

        When I used the 177 KB enablement package (KB5015684) I’d “manually” downloaded on mine, it did not create a Windows.old folder so that actually makes sense.

        After all, as you pointed out, the enablement package isn’t an update, it just enables some “existing but disabled” features that were already in 21H2.

        • #2504289

          I just posted above https://www.askwoody.com/forums/topic/rollback-to-21h2-from-22h2/#post-2504287.

          I did not see this. I guess using (KB5015684) is why there is no Windows.old.

          I have no trouble but what if I do need to go back? What do I do?

          HP Pavilion Desktop TP01-0050 – 64 bit
          Windows 10 Home Version 22H2
          OS build 19045.2486
          Windows Defender and Windows Firewall
          Microsoft Office Home and Business 2019
          -Version 2211(Build 15831.20208 C2R)

          • #2504322

            You uninstall the enablement package and set Windows 10 to 21H2

            1 user thanked author for this post.
            mpw
    Viewing 3 reply threads
    Reply To: Rollback to 21H2 from 22H2

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: