Announcement

Collapse
No announcement yet.

Wndows 10, version 2004

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wndows 10, version 2004

    Total nightmare for me. Good thing I cloned the drive before updating.
    Many shortcuts did not work. RevoUninstaller failed. Fences did not work.
    Older gigabyte motherboard. Hopefully many of you will have better luck.

    Could not rollback using the Windows recovery.
    How long is an idea? Write it down.

  • #2
    I've had it for a couple weeks now. Like the typical massive updates you will have to reinstall most apps. Not a problem. But then I wanted a clean start so I did "Reset my PC". After that the toughest part was reinstalling Edge (Chromium). The installer was overwhelmed and could not download the necessary files. Once I fixed my Microsoft account the new Edge installed perfectly. Wham bam thank you Ma'am.

    Comment


    • #3
      Originally posted by Mike
      Good thing I cloned the drive before updating.
      Same here. I do a full system backup every day and keep the last seven. Before MS half yearly I put a copy of the last backup into another folder in case I need to go back further than seven.

      2004 screwed up my Nvidia graphics and I got many jpg artefacts on my secondary monitor; strangely the primary monitor was OK. MS recognized this with 'older' Nvidia drivers.

      Comment


      • #4
        Similar problem here. I also had a window open at startup with caption "cx_freeze" Said something about python and mentioned power settings.
        I will try again doing a clean install in a few weeks since haven't done that in a few years. Had enough fun today with it.
        How long is an idea? Write it down.

        Comment


        • #5
          Originally posted by Mike Doty View Post

          Could not rollback using the Windows recovery.
          Have you enabled drive protection?
          You may need to manually set a restore point.
          WinX disables drive protection and recovery as a default.
          The world is strange and wonderful.*
          I reserve the right to be horrifically wrong.
          Please maintain a safe following distance.
          *wonderful sold separately.

          Comment


          • #6
            Kurrt,
            Noticed restore points were gone before the attempt to update to 2004.
            Created a restore point and increased size to allowing 10%. Thank you.

            Now I'm running the older 1909.
            Ran chkdsk/f (no problem)
            sfc /scannow found something and corrected it.
            See no problems in device manager.

            I am going to clone then prevent all unnecessary startup programs using MsConfig and clone again then try the update again to 2004.
            There may be also be conflict with cyberpower battery backup software which might be the cx_freeze dialog that popped up (removed it.)
            Putting off doing a clean install (for now) if this works.
            How long is an idea? Write it down.

            Comment


            • #7
              After returning to 1909 I blocked MS from updating for a month but, considering the ten issues MS became aware of, they now check our system first and if a likely problem then we don't get offered an update. I then allowed updates again. It could be that I am not scheduled an update yet, the update is being rolled out over time, or my system has been looked at and a decision not to update has been taken.

              Of course, I could force an update by downloading from MS but I will not do that - I have seen no evidence that the Nvidia issue has been resolved yet; and Driver Booster 7 isn't finding an update.

              If I were you, Mike, I'd allow updates and leave it to MS. Waiting a bit longer for 2004 will not be the end of the world. What a pain it would be to try an update again and get a repeat of your opening post.


              Comment


              • #8
                I'm making the 3rd clone using Macrium Reflect (paid version) that does the fast clone (forgot the name of it.)
                It won't be a pain, I'll just use one of the 3 clones if it fails. Unfortunately, this 3rd clone is doing a full backup which is at 65%.
                David,
                I agree, it this fails, I'll wait. Noticed 2004 update isn't being pushed at me like before.
                How long is an idea? Write it down.

                Comment


                • #9
                  Noticed 2004 update isn't being pushed at me like before.
                  Same here. It would be nice if rather than be told "You're up to date" we were told an update is being held back because there are one or more issues needing to be resolved first. You can do that MS if you put your thinking cap on.

                  Anyway, good luck with your next attempt.

                  Comment


                  • #10
                    I had a problem updating to 2004, everything seemed to go OK but then it would fail at about 80% finished, I reverted my system back about 6 months and then I was able to update to 2004 without a problem, it has been about a week and I have had no problems so far
                    as the salmon fish is compelled to go back to it's birthplace to spawn, so comes a day when man is compelled to go back to it's source.. GOD

                    Comment


                    • #11
                      It worked!
                      Note: I went into task manager and disabled all startup options before updating (which I think solved it since I did this in the past.)
                      I also ran sfc /scannow before updating that fixed a problem.

                      Even Fences started though it was disabled in startup (?).
                      Winver shows 2004.
                      Also noticed One-drive was installed (which has been disabled.)

                      Kurt,
                      Noticed Windows now offers option to restore to previous version of Windows using system recovery. Nice.
                      Created another store point.

                      Thanks everybody!
                      How long is an idea? Write it down.

                      Comment


                      • #12
                        2004 not correctly working with everything.

                        KB 2552925 cumulative update .net 3.5 and 4.8 fails fwith error 80070008.
                        Chrome having troubles.
                        sfc /scannow won't run.
                        dism also fails.

                        Back to Windows 1909 using 1 of the 3 cloned SSD's before the update to 2004.

                        If I were you, Mike, I'd allow updates and leave it to MS. Waiting a bit longer for 2004 will not be the end of the world. What a pain it would be to try an update again and get a repeat of your opening post.
                        David,
                        Good advice, I should have. Gave it a try.
                        Each clone of 1909 was to a separate bootable SSD drive so going back was no problem.
                        How long is an idea? Write it down.

                        Comment


                        • #13
                          Originally posted by Johan
                          I reverted my system back about 6 months
                          GULP!

                          If you ran a software updater you may find that you have one heck of a lot of software that needs updating. 6 months? - flaming heck!

                          Mike, you mentioned that the desktop icons took a while to show but removed that statement. What did you do? Restart?

                          I won't be going anywhere near 2004 until the Nvidia issue is sorted.

                          Added: I was gagging for a cup of tea and posted after your last post, Mike. What a bummer!

                          I wonder how long it will be for MS gets in touch with "Good news - we have fixed the 10 issues with 2004. The bad news is that we have found another three. Bear with us - we'll be back".

                          Comment


                          • #14
                            David, it was Fences not enabled (twice) in task manager startup. I re-enabled there and they appeared at startup.
                            Of course, I'm back using 1909.
                            How long is an idea? Write it down.

                            Comment


                            • #15
                              I must be the odd man out. I updated two systems -- my 3 year old HPOmen i7 laptop, and a >5 year old i7 home made desktop with an nVidia based video card, two monitors, etc... The nly anomloy was on the laptop. It had gone to sleep (waiting for me to acknowledge the upgrade completion, I suppose), and didn't want to wake all the way back up. Complete power off via the power button, restart ,and everything was back.
                              Real programmers use a magnetized needle and a steady hand

                              Comment


                              • #16
                                I updated 2 laptops and 1 desktop 2 weeks ago with 1 USB stick. The only issue I had was my Windows Account was messed up after I did "Reset my PC". Easy fix.

                                Comment


                                • #17
                                  All my VMs updated w/o error. 90% of PC's and laptops updated, all without error. Oddly, the only one not offered the update was my master PC which has the most complex hardware config of the bunch.
                                  <b>George W. Bleck</b>
                                  <img src='http://www.blecktech.com/myemail.gif'>

                                  Comment


                                  • #18
                                    You could always use the trick presented here to prevent a update to the next major version and in that way, wait until it is stable.

                                    https://www.bleepingcomputer.com/new...ws-10-updates/


                                    Comment


                                    • #19
                                      I personally think y'all are weak about not beinng upset with Microsoft
                                      p purvis

                                      Comment


                                      • #20
                                        Which is as much good as crying over spilt milk or being upset with Covid-19. Quite a few pundits have been saying for sometime that MS should issue security patches ASAP but reduce the frequency of feature updates to annually, say, rather than bi-annual. They threw the May 2020 update out knowing full well there were unresolved issues. I think that they were taken aback by the percentage of machines that 'went down the pan'.

                                        Comment

                                        Working...
                                        X