Announcement

Collapse
No announcement yet.

Wndows 10, version 2004

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

  • David Roberts
    replied
    I was talking to a friend of mine about the 2004 update. His reaction was to pause updates for 28 days after telling me his graphics card was an old Nvidia. I told him there was no need to do that - he could block 2004 for as long as the next update if he wanted. I gave him the above script. During a conversation a few days ago I learned that his graphics card was by Radeon. I barked at him saying: "You said you had an Nvidia card." "Oh", he said, "Sorry". Anyway I told him I'd write another script to remove the last one.

    I then had an idea - all he needed to do was change the 1909 to 2004 and Restart. When the next half yearly updates sticks its head over the parapet it will automatically get blocked because we are now using 2004 in the registry. Once the 'dust has settled', so to speak, we can change the 2004 to the next version, lets say 2016 for example, and Restart. When the next update comes out it will get blocked because we have 2016 in the registry and ad infinitum. So, we can now block every half-yearly update and let it through only when we are good and ready simply by changing the version number in the registry and Restarting.


    Leave a comment:


  • David Roberts
    replied
    V1909 and V1903 have been receiving updates for a while. At some point updates for 1903 will cease. Pausing updates up to 35 days will pause everything. I like Mikael T's post because that will pause V2004 but will still allow V1909 updates including, especially, security patches. I edited the registry and then exported the edit and got this.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    "TargetReleaseVersion"=dword:00000001
    "TargetReleaseInfo"="1909"

    I have called that 'StayWith1909.reg'.

    If you want to do the same then Merge the reg into the registry - make sure the last line has a 'carriage return/line feed' otherwise it will not get merged.

    Leave a comment:


  • Mike Doty
    replied
    https://www.windowscentral.com/windo...and-complaints
    I might get mad if I paid for updates and a clean install didn't work.
    I didn't try that since the update is not critical enough to reinstall all programs.
    If programs didn't use the registry would sure make things easy just coping them back.

    I would get mad if rolling back or using a previous version didn't work.
    I would get mad if my clients had to be fixed.

    Computer central says wait as of June 16, 2020.

    Leave a comment:


  • David Roberts
    replied
    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'.

    Leave a comment:


  • Paul Purvis
    replied
    I personally think y'all are weak about not beinng upset with Microsoft

    Leave a comment:


  • Mikael T
    replied
    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/


    Leave a comment:


  • George Bleck
    replied
    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.

    Leave a comment:


  • Jim Fritts
    replied
    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.

    Leave a comment:


  • Bud Durland
    replied
    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.

    Leave a comment:


  • Mike Doty
    replied
    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.

    Leave a comment:


  • David Roberts
    replied
    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".

    Leave a comment:


  • Mike Doty
    replied
    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.

    Leave a comment:


  • Mike Doty
    replied
    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!

    Leave a comment:


  • Johan Klassen
    replied
    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

    Leave a comment:


  • David Roberts
    replied
    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.

    Leave a comment:


  • Mike Doty
    replied
    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.

    Leave a comment:


  • David Roberts
    replied
    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.


    Leave a comment:


  • Mike Doty
    replied
    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.

    Leave a comment:


  • Kurt Kuzba
    replied
    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.

    Leave a comment:


  • Mike Doty
    replied
    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.

    Leave a comment:

Working...
X