New
#560
The following VBScript gives you notification.
Code:Set Job = CreateObject("Microsoft.Update.Session").CreateupdateSearcher().Search("IsInstalled=0 and Type='Software'") Msgbox Job.Updates.Item(0)
The following VBScript gives you notification.
Code:Set Job = CreateObject("Microsoft.Update.Session").CreateupdateSearcher().Search("IsInstalled=0 and Type='Software'") Msgbox Job.Updates.Item(0)
This reg file deletes [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
and then recreates it with the following:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"NoAutoUpdate"=dword:00000000"
AUOptions"=dword:00000002"
ScheduledInstallDay"=dword:00000000
"ScheduledInstallTime"=dword:00000003
Aren't the only items that matter here the first two, NoAutoUpdate, and AUOptions? Why are the two "ScheduledInstall" items there?
That's cool, but they don't seem to be involved with notification, though. Setting ScheduledInstallDay to 0 just means to install every day. And setting ScheduledInstallTime to 3 just means 3 am, I think. Are those the defaults or something? They don't even show up at that registry location for me, that's why I'm asking if they're even necessary to add back in, in the context of this reg file.
Correct, they're all the default settings added and made to the registry when setting it Group Policy.
They should be included though.
Regarding "OPTION THREE Enable or Disable Windows Update Automatic Updates in Windows 10 To Turn On or Off Automatic Device Driver Installation"
FYI, this option still doesn't stop a Windows *feature update* from installing a different driver than the current one you're using. My reading on this problem is that if you've tried a newer version of the driver in the past and a copy still exists in DriverStore, even if you aren't currently using it the feature update will choose *the newer one*, instead. So, I've just gone in to DriverStore and removed such additional drivers using DriverStoreExplorer (it's a free tool available on GitHub). You can also do this on the command line, but DriverStoreExplorer has some safe guards to make sure in-use drivers don't get removed. Hopefully this solves the problem of having to re-install and re-configure a better, but older touchpad driver that I was having to do every time a feature update happened.
Edit: Removing it from the DriverStore also doesn't seem to work, you just get prompted to install the driver update yet again.
Last edited by mmortal03; 12 May 2018 at 19:30.
The "ELAN driver update for ELAN PS/2 Port Input Device" just popped up again in Windows Update, ready to install, so I guess removing it from the DriverStore didn't help. I mentioned elsewhere that I've already tried selecting "No" under device installation settings in Windows, along with registry changes, and neither has worked: Enable or Disable Driver Updates in Windows Update in Windows 10 - Page 16 - | Windows 10 Tutorials
Now, I've just tried the Hide or Show Updates tool from the following, but Windows Update doesn't respond to this and was already dead set on installing it, so hiding it did nothing, and it still installed (I tried restarting the Windows Update service after hiding it, but it still wanted to install it): Hide or Show Windows Updates in Windows 10 | Windows 10 Tutorials
Since I'm on Windows 10 Home, it doesn't seem as if there is a way to block installation of a driver for an individual hardware ID, like there is in Pro in the Group Policy Editor.
Am I out of luck?
Two things:
1. I've been using WUMT with great success until a month ago. All of a sudden it isn't as effective at blocking updates as it used to be. Has anyone else also had that experience -- like maybe MS has tried to write around part of it?
2. I can't find an update to version 20.12.2016. Does anyone know if one exists?
Cheers!
That is a really good question! I'm sorry, I should have thought of that. 1709.