Replies

i’ve tracked down a way to possibly programmatically set notepad.exe to open mht and mhtml files. outlined the assoc and ftype commands w/registry keys here:

https://seamonkey420x.blogspot.com/2019/04/programmatically-associating-mht-and.html

IE still shows in list of apps to open with the first time you open a mht or mhtml file but notepad is set as the default.

hope that helps others that need a fix for a fleet of workstations.

we have been using the 1809 update in wsus that did have the same name except the ending 2019-03B since early Jan (after they re-released it after issues w/user profile and data deletion).  Nonetheless, will wait to hear from others but until then we are declining it and using the one we’ve been using the last two months

thanks for the reply!

We just noticed a newly published Feature Update to Windows 10 in WSUS from 3/28/19.

• Feature update to Windows 10 (business editions), verison 1809 x64 2019-03B, en-us
• Feature update to Windows 10 (business editions), verison 1809 x86 2019-03B, en-u

If you click link in WSUS for info, it will bring you to the 1803 update history page of course.  Is this an updated 1809 feature update or a possibly mislabed update? We have declined in our WSUS since we are in the middle of rolling out 1809 feature updatse to all of our 1607 clients and don’t want to change the criteria that we have tested with.

Anyone else noticing this or know what this is?  TIA!

Just an update after further testing/checking today.  I believe the settings I have are working as they should and we no longer get the “Check for Updates” button.  Even though in settings it says updates are paused, i was able to get an office 2016 update via wsus today on my machine so…. i think my settings are actually fine and working as they should on 1809.

 

thanks everyone who chimed in!

1 user thanked author for this post.

b

b wrote:

seamonkey420 wrote:

1. We want to ONLY use WSUS for windows updates. We have a proper GPO for 1607 and 1703 and even 1803 but on 1809, my settings are yielding the results i expected/that worked previously.

Not? (on 1809)

seamonkey420 wrote:

All of this we were able to accomplish on 1607 and 1703. However I have yet to find a proper Microsoft document talking about the changes to Windows Updates in 1809. I know that one BIG CHANGE is that setting Telemetry to 0 will basically override all WufB policies and let workstation use WU vs WSUS. I have in turn changed that GPO setting from 0 to now 1.

I believe that applied prior to 1809: Windows 10 Dual-Scan enabled when telemetry is set to 0

Correct, i mistyped and forgot the “not working as we want” part.

Most likely will be putting in a ticket w/Microsoft Premiere support.

anonymous wrote:

An update to my prev post: I apparently didn’t RTFA and am noticing exactly this problem and we do use WSUS. Change Telemtry to 0 so i can get the “Check for Updates” button back but when i check for updates it says i’m up to date but when i check on my WSUS side of things, i see that the Nov 2018 CU is showing as needed but not showing on the client so… yes. this appears to be true even with WSUS unless i’m missing a setting in my GPO (we set wsus server address in gpo, the group in wsus it goes to). INSERT FACE PALM.. why do Windows Updates have to be this complex on Windows 10? each feature build changes the behavior.. great… just great…. now how does one get the “Check for Updates” button and also be able to get CU updates for 1809? TIA!

hmm.. it appears 2018-11 CU for 1809 isn’t needed if you pushed the re-released feature upgrade.  I approved the 2018-12 CU for 1809 on my wsus and am now seeing it on my clients.

 

TLDR; i’m an idiot..

well.. if its any consolation, we are still on 1607 and very happy with it and are hoping we’ll be able to stay on it forever.. hehe.. or MS will allow us 1607 Enterprise users to be considered LTSB/LTSC.. we do now have until next spring to update away from 1607.

AlexEiffel wrote:

Right now, it should be clear that there could be two paths for this. Those excited by novelty could beta test Windows as much as they want and improve Windows every six months, adding, changing, removing things based on feedback while the rest of us wait for some less frequent updates. {…}

I have no problem with optional features like this if they are optional, even better if you can use them while subscribing to not storing the searches after you have done them. I understand they might be great to some people, but if I don’t want that, please respect my choice.

TLDR – go back to how we did it in Windows 7 days. let the consumers run ‘beta’ builds of the OS but if a company has paid for and deployed Enterprise edition of Windows; we can opt out of all feature update and just get security updates.  why is it so **** hard for them to understand this; workstations down = loss productivity = revenue losses.  plus, the QCing at microsoft is ****… fix a bug this month, forget next month to refix it in the next CU… sure wish linux was feasible for enterprise.

Edit for content
Please follow the –Lounge Rules– no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

woody wrote:

Diagnostic Data Viewer is nice but, ultimately, not very useful for normal people. What we need is a big “Telemetry Off” switch. Instead, we get little snooping enhancements like killing “Disable Web Search.”

OMG! so much of this!!!! all of these feature updates.. pointless.. every single one introduces major bugs, app compatibility and just device driver breakage..   is Microsoft both deaf and blind in not seeing how much backlash they are getting from real geeks/IT depts/sysadmins?  just let me stay on 1607 and get security patches; zero * given about stupid timeline or ARSO.. what is windows trying macos now?   /RANT

also.. woody, love this blog! you say it how it is and how we feel!

Edit for content.