Tips for the weekend – why are you still on 2004?

Topic

New Reply

Video here For all of you askwoody readers that are still on 2004, after I give the go ahead for patching later on in the month, I’ll want you to do n
[See the full post at: Tips for the weekend – why are you still on 2004?]

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Replies

I am not on 2004 Windows 10. My user agent is set to that on my Windows Xp machine (my last one—other failed a few months back). The user agent tricks sites into think that I am on Windows 1o, the tele-spyware machine created by current hackers works at MS, and sites works with out issue in most cases. Once my Windows Xp machine stops workins, will be using Windows 7 until it stops working. I have 3 windows 7 machines in my storage. Windows 10 is not safe to use in my opinion, which  most will not agree.

Reply | Quote

Same here but using Windows 7 with agent string for Windows 10. Our IT department has classified Windows 10 as unwanted software since has bitcoin miner and keylogger included and are allowed to use only Windows 7 with agent string. MS gave out Windows 10 to everyone for free since they included bitcoin miner that is used with telemetry data to make money for MS.

Reply | Quote

What bitcoin miner is included in Windows 10.  Facts please, not speculation.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Windows XP is not safe to use.  From insecurities to lack of support of newer vendors so lack of support of stronger SSL, it’s really not safe to use when browsing the web.  I’d rather you install a version of Linux than run unsupported operating systems in this day and age.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Alex5723

Reply | Quote

I checked which version of Winows10 I was using and got this from System Info.

Version 10.0.19042 Build 19042

It looks like a really old version but I have no idea what version that is. Can anyone help?

Reply | Quote

Seems to be 20H2 October 2020 Update
https://en.wikipedia.org/wiki/Windows_10_version_history#Channels

Windows 10 Home 22H2, Acer Aspire TC-1660 desktop + LibreOffice, non-techie

1 user thanked author for this post.

Tom

Reply | Quote

Run winver for full version

1 user thanked author for this post.

Tom

Reply | Quote

Susan, do you have to change the target release version if it is set to an earlier version of Win10 prior to doing an upgrade of Win10 using the method you described?

Reply | Quote

No, you don’t have to change the targetreleaseversion setting.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

WildChild

Reply | Quote

Lol, Our PCs are still on 1809,

Why? Stable. Nothing worthwhile upgrading on later releases. Stuff we’ve removed gets restored on later versions. The endless 6 monthly upgrade cycle is too much work for one person with limited time to spend testing each new version. And lastly, each new version comes with too many issues that take too long to sort out.

Reply | Quote

https://docs.microsoft.com/en-us/lifecycle/announcements/windows-10-1803-1809-end-of-servicing

21H2 will only be upgraded once a year. The issues honestly have been sorted out.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Stable–and vulnerable.

I get not doing a feature update every 6 months. The only reason I have is that the last few feature updates have been like 100MB with very few changes–more like regular updates.

But you’ve gotta update sometime. And you’ve had 6 months to a year without security updates if you’re still on 1809.

Reply | Quote

I suppose so, but given I’ve got support until 2025 it won’t be before that.

We’ve managed to get rid of most of the bloatware, and CUs don’t restore it. From 1903 onward all the bloat (and I’m not talking inbox apps), get restored. That leaves me three choices. Stay on 1809. Upgrade to to a later version that has all it’s issues sorted and don’t patch it. Or continue my battle with everyone to move to Linux (The last one being my preference).

I’m still getting updates for 1809 so I don’t perceive any urgency. Latest CUs arrived in WSUS this morning.

Reply | Quote

You sure you aren’t on LTSB?  Because 1809 Windows 10 reached end of service in May.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Dec CU for 1809 is KB5008218 – Build 17763.2366

Reply | Quote