News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • A few smallish gremlins still infest Win10 20H2 and 2004

    Posted on Tracey Capen Comment on the AskWoody Lounge

    Home Forums AskWoody blog A few smallish gremlins still infest Win10 20H2 and 2004

    Viewing 4 reply threads
    • Author
      Posts
      • #2310397 Reply
        Tracey Capen
        AskWoody MVP

        ON SECURITY By Susan Bradley With the release of Windows 10 20H2, May’s Version 2004 has moved into an elder-sibling role. But that doesn’t mean that
        [See the full post at: A few smallish gremlins still infest Win10 20H2 and 2004]

        2 users thanked author for this post.
      • #2310470 Reply
        abbodi86
        AskWoody_MVP

        Regarding the in-place upgrade / repair issue in v20H2 #2306282

        v1909 had the exact same issue at beginning, but they fixed it with compatibility shim (appraiser.sdb or sysmain.sdb)

      • #2310638 Reply
        EP
        AskWoody_MVP

        certain old or outdated Conexant audio drivers still block the upgrade to 2004/20H2 thru WU though Susan did not mention about this in her article

        those devices or PCs with affected Conexant drivers should still stick with the 1909 version until WU or the manufacturer offers 2004/20H2 compatible Conexant audio drivers

        • This reply was modified 2 weeks, 3 days ago by EP.
        • This reply was modified 2 weeks, 3 days ago by EP.
      • #2312283 Reply
        pinky19034
        AskWoody Plus

        I too had the Conexant drivers issue on my older Dell.  I solved that issue by disabling on-board audio in my BIOS.  I was then offered H2 update (from 1909) with the hour.

      • #2312358 Reply
        KevinTMC
        AskWoody Plus

        Glad to see the 2020 versions are getting to be less and less…well, 2020.

        Still rocking 1809 on my two machines though. (They’re on Enterprise, which gives me the luxury of doing so.) I get more fervently “if it ain’t broke…” all the time.

        Probably getting about time to make a move though, even so. There were a few issues with 1909 that I’m not sure ever got resolved…but that’s what I have penciled in as the most likely destination. Unless it would be wiser to jump farther ahead.

        (Any remarks from the peanut gallery would be thoughtfully considered.)

        ---
        Home machines: Windows 7 Home (Group B)
        Work machines: Windows 10 Enterprise (1909)

        • #2312363 Reply
          PKCano
          Da Boss

          At this time, v1909 is the most stable going forward from where you are. Most of it’s quirks have been ironed out.
          I’d wait on v2004 a while longer and v20H2 just came out.

          1 user thanked author for this post.
          • #2314172 Reply
            KevinTMC
            AskWoody Plus

            Thanks for being helpful as always.

            It took a minute to get to it, but I’ve now got both work machines upgraded to 1909. It went smoothly (and in the laptop’s case, even a bit less ponderously than last time).

            There’s the odd gremlin in the system still…but no more than there were beforehand. (Just need to clean up a couple of less-welcome changes and tweaks that the upgrade seems to have pulled behind the scenes…)

            ---
            Home machines: Windows 7 Home (Group B)
            Work machines: Windows 10 Enterprise (1909)

    Viewing 4 reply threads

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: A few smallish gremlins still infest Win10 20H2 and 2004

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