Replies

Actually, Woody might not be wrong. The Server 2019 ISO on VLSC is now named SW_DVD9_Win_Server_STD_CORE_2019_1809.2_64Bit_English_DC_STD_MLF_X22-18452.iso and has timestamps from September 7th, 2019. Note the 1809.2 in the filename.

You’re not running the command prompt as an administrator; it would say Administrator in the title bar if you were.. The easiest way to do it is to right-click the Start button and you’ll see Command Prompt (Admin) as an option.

Open a command prompt as administrator and run the following. Then try installing SyncToy again:

dism /online /enable-feature /featurename:NetFx3 /all

Has to be specific to 32-bit; 64-bit has no NTVDM.

1 user thanked author for this post.

doriel

I’ve used it myself for years so I’m confident that it’s safe.

[steeviebops]

The old Intel GMA video (pre i-series processors) was never officially supported in Windows 8 or 10, in fact Intel went out of their way to block their G45/Q45 drivers from installing on Windows 8 – IIRC they put an empty section in the INF to target Windows 8 and just do nothing. The driver you get from Windows Update is an extremely basic one so you could be stuck here unless you can pick up a cheap and cheerful AMD or NVidia card.

A repeat of the Clover Trail graphics issues I wonder?

• This reply was modified 5 years, 9 months ago by steeviebops.

It’s a tough one. The alternative is to strictly respect the metered connection, not update the machines at all and result in them going EOL in a few months. I don’t know what the solution is, short of continuing to service all builds indefinitely or making LTSC generally available.

anonymous wrote:

Microsoft are still not going to push many beyond Windows 7, or even Windows 8.1 with a third party product to turn all that TIFKAM madness off. It’s a control issue that MS has and plenty of PC/Laptop users that do not like that control over their systems in Microsoft’s hands.

It’s 4 years on and it’s only been by attrition that Windows 10 has barely gained the larger part of the Windows OS versions market share. And Windows 7 is still installed on a very significant number of systems even going on 7+ years after Windows 8/8.1 and Windows 10 were introduced.

MS broke the UI with Windows 8 and never really fixed that completely with Windows 8.1 and folks needing third party software to make things more manageable for 8.1 and with Windows 10 and all that spyware as as feature and forced cloud integration and forced updates that more often than not break things and cost users time and money. So there is third party privacy software for Windows 10 and that should be giving the folks in Redmond some idea of why there is so many still avoiding their latest OS offerings if possible.

Stability has gone out the door with Windows 10 and many are still waiting for some consumer variant of Windows 10 that will bring stability rather than feature creep madness.
Not many more folks are going to be wanting any forced cloud sign in when they log onto their PCs/Laptops and the lack of privacy from having their productive desktop application ecosystem turned into a Smartphone like metrics gathering non productive ecosystem.

It’s that eternal game of settings Whack-A-Mole that’s keeping even more away from Windows 10 and some away from needed security only updates on windows 7 and probably 8.1 as well.
Some have no plans for moving beyond Windows 7 even after it’s EOL in 2020 on the consumer side while the lucky Enterprise/Volume Licensing customers will get the option of purchasing extended Windows 7 security updates until 2023 and having less overall headaches from Windows 10 over that 3 year period. And $350 over 3 years for extended windows 7 support until 2023 is a bargain compared to that Windows 10 breakage and time consuming fixing required.

Microsoft has very little remaining time to get its latest OS working properly for the majority of folks and their PCs/Laptops working for the end users and not for the folks in Redmond. It’s not helping hardware sales to have Windows 7 and 8.1 unsupported on the latest few years of new processor offerings while the Linux Kernel based OS distros have no artificial impediments placed in the way for supporting the latest PC/Laptop and mobile processors/processor features.

I have completely skipped this months(July 2019) “security only” Windows 7 patches as they are not Security Only and hopefully Aug 2019 will be different as I’ll skip that as well if any Security Only patches get any nefarious extras that are not security related. I’ve got one laptop with a Windows 8 Pro license that’s been running Windows 7 Pro via downgrade rights and that laptop is getting a new SSD to replace the spinning rust and Windows 8 pro installed from the Recovery DVDs and an in place upgrade to Windows 8.1 and any security only updates that are telemetry free. And Maybe by 2023 Microsoft will get a clue.

Save yourself some hassle by clean installing Windows 8.1 rather than going the 8-8.1 upgrade route. The 8 key won’t be accepted during the initial install – you could use a KMS 8.1 key to work around that – but you can then use your real 8 key after it is installed.

EP wrote:

The “ExcludeWUDriversInQualityUpdate” registry entry was introduced in the 1607 release of Win10.

That’s true but it wasn’t enforced very well. Despite enabling it in 1607, I had at least two occasions where my touchpad driver was replaced. I need to use v17 of the Synaptics drivers because v19 causes my left touchpad button to double-click when I press it just once. But Windows 10 kept installing v19. Thankfully it hasn’t happened once in 1809 or 1903. Can’t say for 1703, 1709 or 1803 as I skipped them.

That Control Panel setting never worked in Windows 10 despite what you read online. Even in Windows 7, it only prevented Windows from checking Windows Update for drivers when a new device was detected (such as when a USB device is plugged in or powering up after installing a PCI card). The only setting that ever worked for me was ExcludeWUDriversInQualityUpdate.

Thankfully, my 1903 upgrade went fairly smoothly with only a couple of minor issues and drivers weren’t one of them. Forced driver updates had previously forced me back from 1607 to Windows 8.1.

Install KB3138615 manually first and this should speed things up.

Maybe this is too simple but can’t be ruled out.

Right-click desktop background, go to View and make sure that “Show desktop icons” is enabled.

Surely this is a valid usage case for LTSC?