Windows 10 Updates

ChrisJ
Posts: 349
Joined: Sun Oct 27, 2013 3:32 am

Re: Windows 10 Updates

Postby ChrisJ » Thu Sep 14, 2017 9:10 pm

Hi TC :)

The short answer is yes you should be able to hide (or gray out) updates unless their prerequisites are in place -- a needed update is installed or a particular file version is already installed. It will likely require a bit of investigation on your part to pick the most reliable details with these large rollups but it should be doable to hide or better gray out an update if it needs last months rollup to be in place first.

BTW, the dates also act to install updates in order if multiple updates can be run one after the other -- the older dates go first so 20170901 goes first, 20170902 next, 20170903 will run last - kinda cool.

TheApGuy will have more specific details I'm sure, I don't know how much of the old functionality has been changed or removed but you can have a look at the old docs here -->> viewtopic.php?f=27&t=1277&start=20#p5539

Hope this helps some.

User avatar
The Crow
Posts: 18
Joined: Wed Jan 25, 2017 12:12 am
Location: United Kingdom

Re: Windows 10 Updates

Postby The Crow » Thu Sep 14, 2017 10:13 pm

Hi,

I'm aware that Autopatcher currently installs in date order, it's down to users visually seeing the unneeded install within the GUI selection, if a user already has a superseded update installed, the previous update would still show as installable within Autopatcher.

But what actually happens in the background is it silently fails (some generic error like this update is not applicable to your system, which a user wouldn't see with the update running through the /quiet switch) to install as there's a newer cumulative version installed, but the user is stuck in a constant loop everytime Autopatcher Is run that it's available for selection to install again

The most reliable data for me would be the minor build version itself as this wouldn't change until a newer update is installed in this case.

I noticed on a forum that the update I'm having issues with isn't compatible with Windows 10 Home, it might be the rare instance that I just need a way for it to show to non home edition users only

Not sure if this can be done with the current version of Autopatcher, by adding in the checks for greater and less builds, same builds or show just to home or pro users would give me more flexibility for these rare occasions

It would be up to TheAPGuy if it's something he can do or consider doing, not sure of Autopatchers capabilities or possible drawbacks

Maybe using something like the greater or less than suggestions to "manage" the Cumulative Update aspect of things, and the other stuff like flash player update is more relaxed like it currently is now

User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 959
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Windows 10 Updates

Postby TheAPGuy » Mon Sep 18, 2017 3:01 am

hmm... it should be simple enough to get it to accept minor build revision numbers. expect it in a few days.

User avatar
The Crow
Posts: 18
Joined: Wed Jan 25, 2017 12:12 am
Location: United Kingdom

Re: Windows 10 Updates

Postby The Crow » Fri Sep 22, 2017 11:18 pm

@TheAPGuy

Just a quick question How are you currently detecting the latest Windows Malicious Software Removal Tool for Windows 8, 8.1 and 10 - September 2017 (KB890830) within Windows 8.1?

I couldn't seem to find a viable option within the CatRoot folder as searching for KB890830 turns up no search results

It's the first time I've added extra updates into the scripts from the Standalone Updates as I'm still fairly new to Autopatcher Script Development

I also searched the registry for KB890830 which also turned up 0 results. The update is definitely installed as I can see it in the Uninstall Updates section within My Computer section

User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 959
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Windows 10 Updates

Postby TheAPGuy » Sat Sep 23, 2017 5:44 am

Any system that has it installed "should" be installed at this location.
C:\Windows\System32\mrt.exe <-- this will get you a file version as well as install date. We don't detect it this way though... we do it with the registry...

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\RemovalTools\MRT
KeyName=Version
KeyValue=507CBE5F-7915-416A-9E0E-B18FEA08237D

FE854017-795E-4685-95CE-3CCB1FFD743D <-- is Septembers version ID (at least for my Windows 7 and 10 x64)

Give your apm a different unique name since the current one for this is
UniqueID=KB890830_X64
So call yours "UniqueID=KB890830_X64_winX" or something like that. We don't want them colliding in the update tree generation section.

User avatar
TheAPGuy
Site Admin
Site Admin
Posts: 959
Joined: Sun Oct 27, 2013 12:38 am
Location: California
Contact:

Re: Windows 10 Updates

Postby TheAPGuy » Tue Sep 26, 2017 12:47 am

<shameful face> I seem to have forgotten about this.

I have just looked around and it "seems" that the only way to check windows 10 minor build is to actually check registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\UBR = 0x000006b3 = 1715

see if it works for you.

User avatar
The Crow
Posts: 18
Joined: Wed Jan 25, 2017 12:12 am
Location: United Kingdom

Re: Windows 10 Updates

Postby The Crow » Wed Oct 18, 2017 9:01 pm

The windows 10 updates are virtually finalised apart from this showing issue

It appears Windows 10 Home Build 10240 last supported cumulative update was June / July

Where as the Windows 10 Professional Build 10240 has a higher dated cumulative update

Is there a way I can make certain updates show for home or professional only?

I'm not 100% sure if this can be done solely via registry, or if you can query the wmi for home / professional and add a new switch like BN10240H and BN10240P etc

If we can narrow this down quickly or create a method the scripts should be good to go

Would just require a minor edit of the affected. apm files and a quick test for install and detection on my vmware

If this cannot be achieved, the worst case is I may have to split the modules up and have a home only and professional only selection for users only

So maybe 4 standalone builds 2 x 32bit for home and pro and 2x 64bit for home and pro

Or still contain in a single 32bit and a single 64bit with an additional heading / section within Autopatcher


Return to “Windows 10”

Who is online

Users browsing this forum: No registered users and 3 guests