Are you still running Win10 version 1803? Microsoft’s pushing hard to get you to 1903

Topic

New Reply

But you don’t have to take it. If you’re running Win10 Pro (or Education), you can manually move to Win10 version 1809. It’s easy. Detailed instructio
[See the full post at: Are you still running Win10 version 1803? Microsoft’s pushing hard to get you to 1903]

Reply | Quote

Replies

I followed instructions to get 1809.  I put “180” in the second box for number of deferral days.  But I’ve seen three different setting suggestions in AskWoody and Computerworld articles:  120, 180, 190.  Which is the correct setting ? thanks.

Reply | Quote

The number of days changes depending on the length of time from when 1809 was declared ready. You also have to take into consideration that if the deferral days are too short, you will run into the time v1903 was considered resdy.

Today, Oct 21:
It has been about 207 days since 1809 was “blessed.”
It has been about 152 days sicce 1903 was “blessed.”

+ If you set deferral greater than, say 210 days, you will see neither update.
+ If you set deferral greater than, say 155 days, but less than 207 days (that’s were the 180 comes in) you will see 1809 as an update.
+ If you set deferral less than 152 days you will get 1903.

5 users thanked author for this post.

Dan Montague, Lars220, columbia2011, abbodi86, woody

Reply | Quote

thank you for explaining

Reply | Quote

(…. and all of those dates go up by one tomorrow …. who said patching was easy?)

2 users thanked author for this post.

Dan Montague, WildBill

Reply | Quote

I know nothing is guaranteed with these updates, but I assume the issues with 1809 deleting files have been corrected, right? I have backup, but I don’t feel like dealing with losing files.  thanks.

Reply | Quote

That was fixed in 1809 long ago.

2 users thanked author for this post.

Dan Montague, dmt_3904

Reply | Quote

[WildBill]

Not related to 1809, but definitely related to what’s “hot”. I saw this in Google News, from ZDNet: https://www.zdnet.com/article/windows-10-1909-and-1903-these-are-our-new-cpu-requirements-says-microsoft
IMHO, This is a push to get customers to buy new computers. So with 1903 being out for 5 months & 1909 due next month, Micro$oft through ZDNet tells consumers NOW that advanced processors are being required? According to the article, M$ gave ZDNet & manufacturers heads-up in April, before releasing 1903. M$ requires 7th generation processors on AMD machines, & requires 10th generation ‘Comet Lake’ processors on Intel machines. I’m currently running Win8.1 on an Intel ‘Ivy Bridge’ machine.
So other than fighting bugs, has anyone running v1903 on older hardware noticed any slowdown in performance? Or could this requirement for “leading edge” tech be causing “bleeding edge” problems on older machines?! Just throwing this out there…
Last Note: I’m a senior citizen, basically retired on a limited income. Does this force me to upgrade to a more expensive, “hotter, better” machine? Or does it force me to wait out Win8.1 until almost 2023 & switch to a flavor of Linux?

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

• This reply was modified 5 years, 6 months ago by WildBill. Reason: Removed formatting that was copied from an email
• This reply was modified 5 years, 6 months ago by WildBill.
• This reply was modified 5 years, 6 months ago by WildBill. Reason: Removed more unplanned formatting

1 user thanked author for this post.

Fred

Reply | Quote

WildBill wrote:

IMHO, This is a push to get customers to buy new computers. So with 1903 being out for 5 months & 1909 due next month, Micro$oft through ZDNet tells consumers NOW that advanced processors are being required?

Microsoft’s requirements haven’t changed in the last year, and are the same for versions 1809, 1903 and 1909.

But these are for manufacturer’s of NEW hardware being sold with Windows, so should they concern anyone else?

And each requirement for a particular processor starts with “Up through …”; so it’s a limit on the latest CPU, not the oldest:

Company must not use New Processor for Customer Systems without Microsoft’s prior written permission …
The processors listed in the tables below, represent the latest processor generations and models which are supported for the listed Windows Edition. Previous generations of processors and models (indicated by “Up through”), remain supported in addition to the listed processors and models.
Windows Processor Requirements

3 users thanked author for this post.

Dan Montague, WildBill, abbodi86

Reply | Quote

Month after month, the 1803 version has been much more stable than the 1903/1909 combo — which has been hit again and again with net, printer, video, app execution, OS faults, and other problems.  If only MS would support 1803 another 6 months while they work on stabilizing 1903/1909 —

Reply | Quote

Simply keep 1803 until the Microsoft clowns come up with something more stable and less buggy than 1809/1903. Maybe the 20H1 will do. Running an unpatched system for a few months won’t do more harm than a trashed one. Just think first before you click and keep the firewall and anti-malware software in good shape.

Reply | Quote

[EP]

only those using education and/or enterprise editions of Win10 v1803 get another 12 months worth of new updates & support until November 2020 as the home & pro editions of 1803 will be EOLed in November 2019

glad I’m using one of the “higher” editions (like education) as using Pro is not good enough for me

• This reply was modified 5 years, 6 months ago by EP.

1 user thanked author for this post.

Dan Montague

Reply | Quote

WildBill wrote:

Last Note: I’m a senior citizen, basically retired on a limited income. Does this force me to upgrade to a more expensive, “hotter, better” machine?

Since Micro$oft doesn’t care to create an operating system that is satisfactory, I tend to say they are a new kind of streetrobbers.

* _ ... _ *

Reply | Quote

Microsoft has a new way to keep your computer’s firmware from being hacked
The company is partnering with chipmakers on a new initiative called Secured-core PC.
https://www.engadget.com/2019/10/21/microsoft-secured-core-pc/

Reply | Quote

another attempt to stifle Linux??😶

numike wrote:

Microsoft has a new way to keep your computer’s firmware from being hacked
The company is partnering with chipmakers on a new initiative called Secured-core PC.
https://www.engadget.com/2019/10/21/microsoft-secured-core-pc/

🍻

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

I don’t think the Linux 1.8% desktop market share is a huge motivator for Microsoft.

Reply | Quote

b wrote:

I don’t think the Linux 1.8% desktop market share is a huge motivator for Microsoft.

I do think that Linux 90% of OS market share is Microsoft concern.

Reply | Quote

Alex5723 wrote:

b wrote:

I don’t think the Linux 1.8% desktop market share is a huge motivator for Microsoft.

I do think that Linux 90% of OS market share is Microsoft concern.

Not one which prompted Microsoft’s new initiative called Secure-core PCs, which are all laptops:

Explore the new Secured-core PCs

Reply | Quote

I have an old HP Laptop Compaq Presario CQ61. I put SSD drive in before W7 Ultmate 64bit upgrade to 1903. If anything, I am absolutely amazed that the speed has definitely increased cpu speed and processing power for me. I just have not been able to update any further since I upgraded to W10 Pro 64bit. Everytime I go to updates there is a blank page with just dots scrolling across the top of page??? everything is enabled but I just cannot update AT ALL? Yet; everything functions fantastically on & offline for me? So my version that does not update? 1903_18362.295 W10 Pro. I hope someone can tell me I’m not alone & the next update should be seamless integration …(yeah Right; >) Cheers team.

If there is magic on this earth ... it's in the water.

1 user thanked author for this post.

Dan Montague

Reply | Quote

Just wanted to make you aware of a huge RDP issue with Windows 10 1903.

If you RDP into a physical machine, or virtual machine (VMware or Hyper-V) and click the x to disconnect, the VM becomes unresponsive.

If you use local group policy editor, Computer -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment -> Use WDDM Graphics display driver for Remote Desktop Connections (set to disable for the fix)

Huge thread here – >  https://answers.microsoft.com/en-us/windows/forum/all/dwmexe-high-cpu-one-core-on-target-system-after/dbce0938-60c5-4051-81ef-468e51d743ab?page=4&tm=1571715946066

Issue dates as far back as August or even earlier.  Why is Microsoft not fixing this?  Huge problem in VM environments.

1 user thanked author for this post.

Mr. Austin

Reply | Quote

I haven’t experienced this and two others I work with have not mentioned this. I RDP over internal networks into VMWare servers all the time and haven’t experienced this.

Red Ruffnsore

1 user thanked author for this post.

jabeattyauditor

Reply | Quote

My test computer is running win 10  1903 and it breaks a vital piece of custom software written in VB6. The program worked in 1809. Is MS going to fix this. It appears to be fixed in all other OS’s.

mbhelwig

mbhelwig

Reply | Quote

Microsoft hasn’t even officially acknowledged the problem.

Anybody’s guess if they’ll try to fix it. The bug seems to exist with VBRUN300.DLL in 32-bit, which makes it an old problem. Here’s what I said a week ago in Computerworld:

The only solution appears to be uninstalling the latest patch. Microsoft hasn’t acknowledged the bug on its Release Status Information page, so it isn’t clear if Microsoft is even aware of the problem — and it’s anybody’s guess if it’ll ever get fixed.

1 user thanked author for this post.

WildBill

Reply | Quote

[Chris B]

I am  on 1903 on one of my machines, because it is brand new. To avoid the bedlam, I have disabled Windows Update on both of my machines temporarily in Group Policies Editor (gpedit).

Once Woody gives the green light, I think I can replicate the deferral behaviour that we had in 1809 but lost in 1903 via gpedit with the following settings:

Computer configuration>Windows Components>Windows Update>Windows Updates for Business>Select when Preview builds…>Semiannual channel & 200 days (using PKCano’s example above

and

Computer configuration>Windows Components>Windows Update>Windows Updates for Business>Select when Quality Updates…>15 days (using Susan’s recommendation)

I would appreciate it if someone with a better knowledge of gpedit can confirm that this will work.

Many thanks

Chris
Win 10 Pro x64 Group A

• This reply was modified 5 years, 6 months ago by Chris B.

1 user thanked author for this post.

Dan Montague

Reply | Quote

This explanation of the deferral settings may help you. The settings are in Group Policy now, rather than the GUI pulldowns, but the description is the same.

2 users thanked author for this post.

Dan Montague, Chris B

Reply | Quote

I mentioned a couple of months ago that most of our Windows 10 users were still on 1803 and I didn’t want to put users through 2 major upgrades a year so I jumped ahead and have been pushing 1903. Nearly all are now on 1903 and the 9 systems left should be updated before the end of the week at which point all of our Windows 10 users will be on 1903.

Things have gone fairly well with no major issues to report. No issues with any of our corporate software programs. No grumbling or complaints from anyone on the upgrade other than a couple commented on the time it took to upgrade. When pushing via WSUS a system will perform most of the upgrade behind the scenes. Users only have sit through a half hour or less of downtime unless they go to Windows Update manually to initiate the update.

The only issues we had were the original broken Cortana search and a couple had issues with the start menu but those issues are no longer a problem. KB4517389 is still a concern for me and remains not approved for users.

This is not a recommendation but a decision based on corporate related considerations. Pushing 1809 may have been a more prudent decision but I’ve managed to avoid a second round of upgrades and we’re set for a while on supported versions of Windows. And a new standard for the organization has been established. I no longer have to manage updates for any previous versions of Windows 10 as well.

Red Ruffnsore

2 users thanked author for this post.

Dan Montague, woody

Reply | Quote

I’m gradually warming up to 1903.

To me, the big benefit is the ability to defer patches. Everything else is just fluff. Yes, I’m saying the “feature updates” in 1809 are really, really lame. (The Win+V multiple clip clipboard being the only really useful feature – and there are a zillion free programs that’ll do the same thing, but better.) The only thing 1809 brings to the game at this point is relative stability, and an automatic “Get out of Jail free” card to keep the pushed upgrade to 1903 at bay.

Let’s see if this month’s second cumulative update to 1903 breaks anything important.

2 users thanked author for this post.

Dan Montague, WildBill

Reply | Quote

Still have around 100 Windows 7 machines that need to be replaced so I’ll still have something to do until years end. 🙂

My personal opinion is 1903 originally was not too bad but the updates that were released later have created more problems as opposed to fixing problems.

Red Ruffnsore

1 user thanked author for this post.

woody

Reply | Quote

woody wrote:

I’m gradually warming up to 1903.

Magic:

b wrote:

Not to worry though: When 1909 arrives in a week or two it will become the big bad ogre to flee from and then 1903 will somehow magically become the one to hold onto at all costs.

 

woody wrote:

To me, the big benefit is the ability to defer patches.

You mean pause. It doesn’t help anyone when you keep using the wrong word.

Reply | Quote

You are correct. Pause updates.

“Defer” is the term used in much (most) Microsoft documentation. It was also used in all previous versions of Windows.

‘Course I could’ve said “delay” and brought down the house…. 🙂

3 users thanked author for this post.

Dan Montague, Chris B, WildBill

Reply | Quote

woody wrote:

“Defer” is the term used in much (most) Microsoft documentation.

… when defer is what they mean.

But “Pause” when they mean pause:
Manage updates in Windows 10

Reply | Quote

I just clean-installed 1903 on a test machine.

The Windows Update advanced options pane also shows “defer” per the screenshot above.

If I change any of the settings, the pane will disappear (for reasons still unknown and undocumented). But as long as the settings are untouched, MS still uses the term “defer”

MS also uses the term “defer” in the Group Policy settings.

What we’re seeing isn’t a difference in terminology or meaning. We’re seeing an internal inconsistency in Microsoft’s documentation. Again.

1 user thanked author for this post.

Dan Montague

Reply | Quote

Mr. Natural wrote:

I mentioned a couple of months ago that most of our Windows 10 users were still on 1803 and I didn’t want to put users through 2 major upgrades a year so I jumped ahead and have been pushing 1903.

We’ve done the same, for the same reasons. No major issues so far.

2 users thanked author for this post.

Dan Montague, Mr. Natural

Reply | Quote

1803 Home User Upgrade to 1809 Home via the 1809 ISO. This is what I intend to do. Hopefully you can still get the 1809 ISO.

https://www.howtogeek.com/427223/how-to-download-a-windows-10-iso-without-the-media-creation-tool/

I got it by changing the FireFox UserAgent to be non-Windows and downloaded the ISO.

Reply | Quote

original Woody post: https://www.askwoody.com/2019/hedge-your-bets-download-an-official-clean-copy-of-win10-version-1903-build-18362-356-and-save-it-for-a-rainy-day/

Reply | Quote

Good thing:  I have a great script within my organization that can copy the Win10 Pro 1809 ISO image from a share to people’s systems, mount it, and run a full feature upgrade; the ISO is deleted by a second follow-up script six hours later.

Bad thing:  The Win10 1809 is causing the dreaded “mapped drives” issue where the network connection isn’t completely live at domain login, causing the group policy drive mappings to fail unless a user actually clicks on the drives themselves in File Explorer.

Anybody know if slipstreaming the latest Windows 10 cumulative updates might fix this?  I’m tempted not to do more Win10 1809 upgrades, this is a pretty big deal (especially for users whose MS Office “Recent” files points to drives that didn’t map, making them do one click per map in File Explorer).  1803 certainly doesn’t have this issue, and Microsoft was supposed to have an update in November 2018 to fix this, but I’ve had a few systems I fully patched after the install that are still having the issue.

We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in support, we do not retreat.
We live for the LAN.
We die for the LAN.

Reply | Quote

Memo to me and to others; it takes two patch rounds, but once the cumulative updates are installed, the issue goes away.

I plan to slipstream the cumulative updates for Windows 10 1809 into a new ISO to prevent recurrence of the issue.  I’ll test and report back.

We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in support, we do not retreat.
We live for the LAN.
We die for the LAN.

Reply | Quote

If you use the Media Creation Tool to create the ISO, you will get a later Build that is past the drive letter problems. You can do this on one PC and use it on all of them.

You must have had an early ISO (Build).

Reply | Quote

That’s how I created this one, but it was some time back.  I do have the Media Creation Tool for 1809, so I’ll look at that too.

We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in support, we do not retreat.
We live for the LAN.
We die for the LAN.

Reply | Quote

Speaking of pushing, Microsoft is planning to deliver Chromium Edge to replace inbox Edge on Windows 10 versions 1903, 1809, 1803, 1709, when Stable release is ready

Windows updates to support the next version of Microsoft Edge

to block it

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EdgeUpdate]
“DoNotUpdateToEdgeWithChromium”=dword:00000001

Reply | Quote

Hello,

I’m on windows 10 PRO 1809  32bit  with PC with Legacy BIOS mode 
Secure Boot State    Unsupported

PC 32 bit windows 64bit capable.

Can i upgrade to 1903 or 1909?

The article below says

“Windows 10 for desktop editions and Windows 10 Mobile and IoT Core must boot into UEFI mode by default and ship with UEFI Secure Boot enabled. System firmware must be compliant with the UEFI Specification Version 2.3.1 or higher”

docs.microsoft.com/nl-nl/windows-hardware/design/minimum/minimum-hardware-requirements-overview?redirectedfrom=MSDN

Thanks!

Reply | Quote

Jones55 wrote:

Hello,

I’m on windows 10 PRO 1809  32bit  with PC with Legacy BIOS mode 
Secure Boot State    Unsupported

PC 32 bit windows 64bit capable.

Can i upgrade to 1903 or 1909?

The article below says

“Windows 10 for desktop editions and Windows 10 Mobile and IoT Core must boot into UEFI mode by default and ship with UEFI Secure Boot enabled. System firmware must be compliant with the UEFI Specification Version 2.3.1 or higher”

docs.microsoft.com/nl-nl/windows-hardware/design/minimum/minimum-hardware-requirements-overview?redirectedfrom=MSDN

Thanks!

First, what kind of PC is it?  And to clarify, did you say you were running a 32-bit version of Windows 10 at this time?

If you’re running 32-bit Windows 10, I’m guessing you upgraded from 32-bit Windows 7.  This means your system is likely very old. Add to it the message you’re getting about a Legacy BIOS, and unless you have a PC that can switch to UEFI mode (uncertain), it looks like you may be at the point where this system should be replaced.  It’s probably at least ten years old if it was running Windows 7 32-bit when you purchased it, and it’s going to get harder and harder to keep it compatible with Windows 10.  Buying a new machine will mean Windows 10 is preinstalled.

Many think Windows 10 never should have been made in a 32-bit option, simply as everything is moving forward to 64-bit.  If you are unwilling or unable to upgrade to a new system (and your system is this old), you’d be best backing up your system, creating Windows 10 64-bit install media, and formatting/reinstalling a 64-bit version of Windows 10, in my opinion. This would allow you to use more than 4 gigabytes of RAM, possibly increasing your performance.

We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in support, we do not retreat.
We live for the LAN.
We die for the LAN.

Reply | Quote

Jones55 wrote:

The article below says

“Windows 10 for desktop editions and Windows 10 Mobile and IoT Core must boot into UEFI mode by default and ship with UEFI Secure Boot enabled. System firmware must be compliant with the UEFI Specification Version 2.3.1 or higher”

docs.microsoft.com/nl-nl/windows-hardware/design/minimum/minimum-hardware-requirements-overview?redirectedfrom=MSDN

That document is for vendors to design new hardware (which they want to sell with Windows 10).

Reply | Quote

thanks Doug and b,

yes your right, the PC is very old and i upgraded from w7 (created GenuineTicket and used that for 1709) , to first 1709 then 1809(still using w7 too) now in triple boot with linux..trying debian and ubuntu… have been learning the past month  😉   hey want to depart from w10 in the future.. and use w7 offline, and yes will get a new system in the next year or so..or maybe somewhat later… if linux keeps running like it does now

HP dc-5800 microtower.

speccy:

Motherboard
Manufacturer    Hewlett-Packard
Model    2820h (XU1 PROCESSOR)
Chipset Vendor    Intel
Chipset Model    Q33
Chipset Revision    A2
Southbridge Vendor    Intel
Southbridge Model    82801IB (ICH9)
Southbridge Revision    02
System Temperature    33 °C

4GB RAM

Threads    2
Name    Intel Core 2 Duo E8200
Code Name    Wolfdale
Package    Socket 775 LGA
Technology    45nm
Specification    Intel Core2 Duo CPU E8200 @ 2.66GHz
Family    6
Extended Family    6
Model    7
Extended Model    17
Stepping    6
Revision    C0
Instructions    MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, Intel 64, NX, VMX
Virtualization    Supported, Disabled
Hyperthreading    Not supported

Going by the answer of b and yours, i think its still possibe to upgrade from 1809 to 1909 but time will be running out..

If i were to upgrade from 32bit to 64 bit version w10, that would mean i have to do a  clean install from an ISO ? I ques i could not use the same GenuineTicket in that case

Up till now i didnt validate through a microsoft account. Used a loader on w7

Thanks ur help is appreciated

Reply | Quote

If you upgraded from 32-bit to 64-bit Windows, it would require a clean install; you would need to create USB install media, boot from it, and format the existing disk.

Your system would not require a new license, as it would be the same Windows 10 license.

If that 4GB memory is a single 4GB module with one memory slot free (as opposed to two 2GB modules), and you are intending to use the system for any significant period of time, I would recommend finding a second 4GB memory module (easily available used for very little money) and upgrading the system to 8GB of RAM at the same time.

The system will not have a UEFI BIOS available; as a Core 2 Duo based system, it is 1-2 generations old before these started being an option.  Windows will support legacy mode however.

We are SysAdmins.
We walk in the wiring closets no others will enter.
We stand on the bridge, and no malware may pass.
We engage in support, we do not retreat.
We live for the LAN.
We die for the LAN.

1 user thanked author for this post.

Jones55

Reply | Quote

Thanks Doug,

“Windows will support legacy mode however”  good to hear that, that was my main worry.b hinted on that earlier i believe. Also nice to hear i can just use the current GenuineTicket in case of a 64bit fresh install.

At the moment got 4x 1GB RAM. So switching RAM would be costly for this old machine. It’ll do for now.When i depart from w7 ( at least being online with it) i will disable the meltdown\spectre patches so the system will run faster.

I believe (correct me if im wrong) spectre patches were hardware (CPU, CHIPS) based and meltdown were sofware based

In case of a new PC,  is there site availlable where i can  get good info on CPU’s witch are not vulnerable to the spectre and meltdown ?

Thanks for ur input.

Reply | Quote

Spectre and meltdown patches are all software – a hardware upgrade would be taking the CPU out and replacing it.
Given we have yet to see one of those exploits I would remove the patches anyway.

cheers, Paul

Reply | Quote

Paul T wrote:

Spectre and meltdown patches are all software – a hardware upgrade would be taking the CPU out and replacing it.
Given we have yet to see one of those exploits I would remove the patches anyway.

cheers, Paul

In the interests of clarity, Paul T is (correctly) referring to BIOS updates as also being software patches.

Reply | Quote

[EP]

aww crud woody. 🙁

I recently turned off group policies of deferring feature updates from gpedit.msc on a test machine running 1803 enterprise, then ran a WU scan and while it was downloading the recent .NET 4.8 Oct. 2019 updates for 1803, it also was downloading the “feature update to 1903” [oh no! 🙁 ]. I immediately pulled my internet connection and rebooted to prevent WU from completely downloading the 1903 feature update (phew that was close)

looks like MS really wants to upgrade anyone using 1803 (for those who have not set any feature update deferrals in either the windows update settings app or from gpedit.msc) out of there and onto more recent versions like 1903, regardless of what 1803 edition being used [yup even the higher editions like education and enterprise might get an unexpected feature update if those feature update deferral options are not set]

so I went back to turn on the feature update deferral period and set it to a full 365 days on 1803 enterprise.

• This reply was modified 5 years, 6 months ago by EP.
• This reply was modified 5 years, 6 months ago by EP.

1 user thanked author for this post.

woody

Reply | Quote

Hmmmm….

To recap, you have an 1803 Enterprise machine that isn’t hooked up to an update server.

You set 1803 to Semi-Annual Channel, 0 days for features, 0 days for cumulative updates.

You click Check for updates, and the machine started upgrading to 1903.

If that’s right -????? – then it’s doing what I would expect. You’re inviting 1903 by using SAC and 0 days on feature deferral.

Or did I miss something?

Reply | Quote

As a PS to this:
My v1803 Pro, with Feature deferrals = 365 and Quality deferrals = 0, is still offering only CUs, SSUs and .NETs. No sign of 1809 or 1903, even in wushowhide.

I am going to let it ride till Dec Patch Tues before I upgrade to 1809, just to see if it lets me pass EOL.

1 user thanked author for this post.

woody

Reply | Quote

Should be an interesting experiment!

I don’t have 1803 on any bare metal machines any more, and I’ll be watching your results closely.

Reply | Quote

I will no longer upgrade this computer (currently on 1903, so far nothing bad)   but I thin it will be the last feature update I will install since I plan to buy a new computer.

 

Also fellow loungers, remember that the point of the new windows versions is to force us to buy computers.

Just someone who don't want Windows to mess with its computer.

Reply | Quote

[Paul T]

New windows versions run on old hardware as evidenced by the posts here, but a sparkly new box is always a good idea!

cheers, Paul

• This reply was modified 5 years, 6 months ago by Paul T.

Reply | Quote