• Cannot update to 23H2 because of BITS error

    Home » Forums » AskWoody support » Windows » Windows 11 » Windows 11 version 23H2 » Cannot update to 23H2 because of BITS error

    Author
    Topic
    #2628175

    I have a Lenovo ThinkBook, bought just last year. Windows 11 Pro, 22H2. It won’t update to 23H2. Windows Update troubleshooter gives me an error message about the BITS service everytime. I tried every trick I found on Google (Windows troubleshooters, DISM, sfc /scannow, and many many more). The problem persists. Should I just do a repair-install ?

    Viewing 5 reply threads
    Author
    Replies
    • #2628232
      • #2628235

        Already did, multiple times. It says it corrected all problems, but when I try to update to 23h2, even though I checked “Get the latest updates”, it won’t work. So I use the Windows Update Troubleshooter and the BITS troubleshooter again, get the same messages  (errors detected and then errors resolved), over and over. Do you think the repair-install would surely solve the problem ?

    • #2628237

      Since you’ve tried the built-in troubleshooters repeatedly with no success, what is the exact wording and error code you’re getting about the BITS service from Windows Update? A reply with a screenshot should be able to answer those questions in one fell swoop.

      Knowing those answers will enable folks here to better help you. Knowing the contents of the error message and specific error code that comes with that message can help determine if an over-the-top repair install is the best solution, or if there’s something else to try that doesn’t involve reinstalling the OS right on top of itself.

      EDIT: Here’s another question that just came to mind to help with troubleshooting: After the BITS and Windows Update troubleshooters completed their tasks, did you first reboot the computer before trying to use Windows Update again? This answer can help with further troubleshooting efforts by those here, so they can better help you out.

      • #2628244

        Bob99, first, thanks for your patience.

        Second, I did reboot after every intervention I made : so after WU Troubleshooter, then also after BITS Troubleshooter, then after DISM, then after SFC / scannow, etc.

        Third : I’m attaching 2 png files and a PDF file showing the results of the Windows Troubleshooters. But they’re in french, since I’m a francophone and my Windows Display language is french. By the way, I wonder if I’m having problems with feature updates because the default language of Windows when I bought it from Lenovo was US english, and I had to change the language aftewards to French Canada ?

        Note : you will notice something strange in the PDF that shows to WU troubleshooter results. Under Collecte de données (data collection ?), it says that I have Windows 10. When in fact, as my settings show, I have W11 :

        Édition    Windows 11 Professionnel
        Version    22H2
        Date d’installation    ‎2023-‎05-‎23
        Version du système d’exploitation    22621.3007
        Numéro de série    MP299EQK
        Expérience    Windows Feature Experience Pack 1000.22681.1000.0

         

         

        • #2628276

          Note : you will notice something strange in the PDF that shows to WU troubleshooter results. Under Collecte de données (data collection ?), it says that I have Windows 10. …

          Try opening a Command Prompt in Windows 11 and at the top of the black command line window that opens, it should say “Microsoft Windows [Version 10.0.22621.3007]”, and the next line should say that it is “(copyright) Microsoft Corporation. All rights reserved.” That is your proof that you’re actually running Windows 11 because that’s the actual version number or build number of your version of Windows 11, even though it starts with a “10.0”.

          As a reference, the build numbers for Windows 7 actually started Windows 6.0.(I don’t remember the rest because it’s been too long).

          Since I now see (after rereading your original post) that you’ve tried running sfc /scannow and DISM as well with no success to resolve your problems with a lack of updating to 23H2 from 22H2, I agree with Paul’s statements below, and an over the top repair installation may very well solve your problem(s). It might even leave you with 23H2, emphasis on might. If it doesn’t then you can try taking a look in Windows Update once the over the top procedure’s done to see if it’s waiting for you to download it and install it.

          • #2628277

            Hi Bob99 !

            The command prompt shows : Microsoft Windows [version 10.0.22621.3007]
            (c) Microsoft Corporation. Tous droits réservés.

            So I’ll do the repair-install and see if it solves my problem. Thanks for taking the time to help me. Greatly appreciated. I’ll mark the post as resolved if all goes well.

             

             

    • #2628269

      When all else fails, install over the top / repair.
      https://www.askwoody.com/newsletter/free-edition-how-to-do-a-windows-11-repair-install/

      cheers, Paul

      • #2628270

        Yeah… that’s what I thought.

        As for feature updates, I still wonder if there’s a conflict between the default language of the original Windows 11 version (en-US) and the language I installed afterwards (fr-CA). I read somewhere it could prevent a user from reinstalling windows from an ISO file. Like in my case, I would have to use an ISO file in english to reinstall the OS, and then change the display language in the settings.

        In any case, I’ll wait a few days and if I can’t find any other solution, I’ll go for the top /repair. I’ll then mark this post as resolved (if all goes well !).

        Thanks for taking the time, you and Bob99.

        • #2628272

          Language files are just an overlay and shouldn’t prevent a reinstall. Sounds like FUD to me.

          cheers, Paul

          1 user thanked author for this post.
      • #2628282

        One last question (I hope). Since I grabbed the ISO file I have for Windows (22h2) in may 2023, should I instead use the Windows 11 installation assistant (23H2) for the top/repair like Susan suggests in her article ?

        • #2628316

          Yes, because there have been lots of updates since then and you don’t want to have to reload too many.

          cheers, Paul

          1 user thanked author for this post.
    • #2629164

      So I finally reinstalled Windows with the installation assistant and got upgraded to 23h2 at the same time. I was worried during the process because I was never asked if I wanted to keep my data and apps ! But everything was there at the end. But… just to be sure everything was back to normal, I ran Windows Update Troubleshooter and BITS Troubleshooter and got the exact same messages about errors related to the BITS service… So, I’m not sure I’ll get future security updates or feature updates. Back to square one… sigh !

      1 user thanked author for this post.
      • #2629168

        So I finally reinstalled Windows with the installation assistant and got upgraded to 23h2 at the same time.

        GREAT! 👍

        But… just to be sure everything was back to normal, I ran Windows Update Troubleshooter and BITS Troubleshooter and got the exact same messages about errors related to the BITS service… So, I’m not sure I’ll get future security updates or feature updates.

        So, you’re back in the same boat, but with a new coat of paint, so to speak, in that at least you got the update to 23H2. I wouldn’t mark this as solved just yet since you still have the same problem as before, in that you might not have full functionality of Windows Update when 24H2 gets released for Windows 11 late this year, I.E. it won’t show you the availability of 24H2.

        To see just where you stand with Windows 11 right now, open up a command prompt and look at what it says for your current version number. If you’re fully up to date with the monthly patches including the one that was released earlier this month on the 9th, you should see 10.0.22631.3007 for the version number. This will indicate that you’re on 23H2 and that you have the monthly update that was released on January 9th installed.

        • #2629182

          Hi Bob99,

          I just checked the version with CMD, and it is the latest version:  10.0.22631.3007.

           

           

          1 user thanked author for this post.
      • #2629171

        @Paul-T

        Is it somehow possible that the over-the-top install didn’t touch the Software Distribution folder at all and just left it intact as part of the “leave all my settings and documents intact” thing?

        Since Andy is nearly back in the same boat, as he’s described things in his post just above, I’m trying to think outside the box to come up with a solution.

        I’ve had to use the WU troubleshooter in Windows 10 in the not too distant past on one of my machines, and it allegedly found problems with both WU and with BITS and fixed them, but then found the very same ones again and allegedly fixed them again. This went on for 3 times before I wound up fixing things by wiping the Software Distribution folder and letting WU rebuild it. After a short while, things returned to normal with respect to what was available and what was hidden through my use of my preferred update hiding solution, wushowhide.

        • #2629186

          Before I reinstalled W11, I did wipe out the software distribution folder, but despite that and all the other things I tried, Windows Update would not offer me the upgrade to 23h2. It’s not that I wanted it so much, it’s that I’m worried I’ll have to do the same thing again to get next feature updates. I had the same problem to get 22h2 last year, but I was able to upgrade from 22h1 to 22h2 manually at the time. I’m at a loss here.

        • #2629329

          I don’t have knowledge of which things Windows leaves, but you would hope update stuff would be “fixed”.

          Given the continuous error status of WU/BITS it may be a furphy. Wait until the next update to see what happens.

          cheers, Paul

    • #2629352

      Windows Update determines if your machine can upgrade to 23H2. You could have some third-party software which is considered a blocker. Or, you could have a driver which is considered a blocker. Microsoft is not very forthcoming about what it considers to be a blocker. While you can and have successfully done a manual upgrade, WU probably still has an issue to be resolved.

      Do you run third-party security software?

      Are your drivers up-to-date?

      Is the BITS service set to start automatically?

      --Joe

      • #2630943

        Hi Joep517,

        I use Defender, no third-party security software.

        I don’t update my drivers through Windows but through Lenovo Vantage (my laptop is a Lenovo ThinkBook).

        The BITS service is set to Automatic (delayed). Which is apparently the default setting.

    • #2687644

      I reinstalled Windows (over the top repair). Thanks for your input everybody.

    Viewing 5 reply threads
    Reply To: Cannot update to 23H2 because of BITS error

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

    Your information: