Windows 10: Spring & Fall Update Issues (Win10 Pro)

Hear me out on this.
I recently bit the bullet an installed the Fall Update (v1709) by doing so I had all sorts of event viewer errors (that I had pretty much straightened out with v1703) trying for several days to resolve these issues (besides the EV errors,DCOM, Miracast etc) like in settings that were grayed out with the ''some settings are hidden or managed by your organization'' that were not present with v1703 (ex: Lock Screen grayed out, Feedback & diagnostics, Privacy grayed out just to name a few) plus the fact the system seemed sluggish overall. What got me is I am the Administrator an belong to no organization...did windows somehow think I was on Enterprise or some such thing?
I got fed up an reinstalled v1703 the system went back to being 'perky or snappy' again no Miracast errors no DCOM errors no settings grayed out. What's the deal on this behavior any ideas?

:)

 

Creators Update should be called Windows 11

You could well be right with the terminology. MS have determined that Windows 10 will be the last number for their OS. This will receive two major (feature) updates during the year, in spring and fall. The Creators update v1703 was the spring update and
the Fall Creators update v1709 is the fall update. (this is just an example for 2017)

There are previous large updates for 2016. But this is something we will have to get used to.

 

Will Spring Creator's Update Fix Issues With Fall Creator's Update Version 1709?

I've been having major issues with the most recent Windows update (version 1709), particularly with my WiFi IP addresses not existing to Windows. Does Microsoft know about the issues with the most recent update? Will it fix the issues I'm having? Any idea
when the resease date of the next update will be? My laptop is entirely unusable without Internet so I'm hoping it will get fixed soon.

 

Hello there. I see you have a custom built tower. What did you originally install on it pre-1703? Did you update to 1709 via windows update or clean install? Do you use 3rd party maintenance software including a Registry cleaner?

Yes, there are only two editions that will have that phrase. Enterprise or Insider.

 

I originally had W7 Pro on an SSD (that I just unplugged from an older HP CTE) put it in the new build, then did the free update in 8/2015, got the new bare bone build up an running, then after a few months of running Win10 Pro (using the Media Tool .iso) I then did a fresh install. I've kept all the .iso's on an external hard drive just in case I have to revert. I've only reverted back to Redstone 2 after trying the Redstone 3 or Fall Update due to all the issues. I was using the version numbers as a short way to explain which ones I was talking about. Each an every install an update since the fresh install has shown my OS to be Windows 10 Pro.
The first time I did the Fall Update I did it thru windows update had issues so I got the .iso then did a 'refresh' keeping my apps & settings an still had issues. I have been loath to do another complete fresh install due to all the programs I have in the OS's registry files not to mention documents an such even though they are on separate hard drives (4) they all have some sort of references in the C:/drive OS...it would take many hours to start all over again. I think I know where this is leading that my issue is to do a complete fresh install of the OS.

 

And all of these 10 OSs activated? Not making a judgement call here. It's your business. It seems to me you may have violated the EULA when you placed the SSD from the HP into your new build. Assuming the HP's W7 was an OEM license. That's what may be haunting you is that OEM license. The server sees that and may restrict the OS this time around.

 

You may be on to something there.
Checking activation thru settings it says 'Windows is activated with a digital license' an yes my original OS was thru HP an come to think of it I had a lot of run around back in W7 days. HP would say go to MS, MS would say go to HP. I would say you guys sold it to HP, MS would hem an haw then give me those 5 sets of 5 alpha-numeric strings to re-activate when times called for it. I remember going thru that months prior to the W10 update process on the bare bones build.

 

If it has digital license, then that may not be the problem.

As much as I know it's a PITA, that may be the solution. More often than not a feature update drags along broken code. As an Insider, I had an update that didn't load all the code, but yet ran. A system image repair fixed it. You may want to try and repair it before taking drastic measures.

 

Isn't a refresh the same as a system image repair? Both use the .iso right?

 

FWIW.. I too had all kinds of strange issues with an upgrade to FCU... Clean installed and all good. Still, I don't get this tho' -- btw I don't mess with Gpedit -- but have this "managed by your organization" crap





Just to be clear... I'm not on Insider and this is not a mobile device - Updates are not blocked.

 

I was referring to Admin Command Prompt using command for DISM > Dism /Online /Cleanup-Image /RestoreHealth

There's startup repair: Run Startup Repair in Windows 10 Performance Maintenance Tutorials

There's refresh as you speak of: Refresh Windows 10 Installation Upgrade Tutorials

 

@ Superfly yeah I'm perplexed at what windows thinks too..I am the Admin am not with any organization (personal PC) yet things come with that same caveat...weird.
@ HippieGypsie I've done those DISM things when I had FUD installed... ..did the 'refresh' with the FUD .ISO mounted.
I've also run startup repair from windows boot (although I had no startup issues at the time) tried all those things with the FUD (1709) to no avail an by no avail I mean all the 'hidden management' deals, nor did it stop all the Miracast & DCOM error events. I fiddled with all sorts of tips & tricks googling Miracast & DCOM errors, deleting things in registry (EndOfLIfe) taking DCOM GUID & AppID ownership that all seemed to make matters worse in FUD.

That's when I went back to the 1703 version.

 

This particular 'managed...' message with the 'view configured update policies' link beneath it is triggered if curiosity ever got the better of you and...

remove msg "some settings are managed by Org" in Windows Update

Oddly, it is only Pro that has this problem, Home doesn't say 'managed...' however many times you tick the box. For this particular problem...

View Configured Update Policies in Windows 10

...and never, ever, tick that box again *Smile

 

Great info, Bree. Added to Favorites. *Smile

 

Thanks *Smile