New
#270
In case no one has noticed yet, Update turned Fast Boot back on, and I had to boot twice this morning. Went in and turned it back off!
Microsoft, quit messing with my settings!
Reported via Feedback.
Just completed a clean install on Hyper-V from my UUP created ISO. The process was smooth as a baby's bum. Took 15minutes from configuring the VM, installing using iso boot method and finally getting into enhanced session of a fresh install. Impressive!
Maybe so, Dencal, but there's no reason for MS to change my settings.
Thing is, I'm here to tell Microsoft what I want; that's why they "hired" me as an Insider. They want to know what I think, want, need and like. Period! Bug or not, I don't recall my instructions saying that I can only report bugs.
Are they going to automatically change settings when Retail versions of Windows 10 are released? What about all those corporations that will eventually move to Windows 10; will their settings be changed with each Retail update of Windows 10?
Microsofties aren't sitting up there with a smirk on their collective faces and saying, "You'll take what we give you and like it!" No, instead, they're telling us they want to know what we think, need, want and like.
I can see Microsoft installing default settings with a clean install, but not with an update. I think we've all had practice enough changing things back to what we've already chosen as our defaults.
A clean install should have every default Microsoft deems necessary or just recommends.
An update/upgrade should not change defaults already set in the OS that's being updated/upgraded.
Me? I think they haven't figured out how to leave my settings alone yet!
There is a big difference between an update and an upgrade. Your upgrade will always have the defaults that come from MS as this is how the new version is intended by Microsoft to be used as default. There are ways to work around those defaults, but it involves editing a lot of group policies and applying those to the upgraded system.
An alternative is to create a registry patch file that contains the default you want for each and every setting you wanna make sure is set to your value. Then after each new upgrade just run the Reg file and voila, all the settings are updated to YOUR values.
Yes, there is a difference between an update and an upgrade; thing is, each update is (for me) a mini upgrade. And since we're testing all facets of Windows 10, the most likely scenario will be some kind of upgrade, especially to those in the corporate and small business world. There will be clean installs of Windows 10, of course, but by and large, upgrade will be most likely.
There are some defaults I wouldn't touch with a ten foot pole, Slice, and there are others that Microsoft has enabled changes for.
For the longest time, MS changed my default browser from Firefox to Edge. They re-enable Fast Startup (I called it Fast Boot) which I have turned off because with it enabled, I have to boot twice to start the computer. System Restore is turned off by default, which is something I would never expect to be done, but, well . . . For a number of updates, my Registry was changed so that I couldn't get my Insider Builds of Office 365 2016; with each update, I had to go into the Registry and change the key. It's no longer changed after each update now.
Those are the kinds of defaults I'm talking about. I'm not into going deep into the OS and editing group policies and such that I know nothing about. I'll let the 'sperts do that.
Going from one build number to another is an upgrade. Applying a cumulative patch is an update.
Settings should not be changed with an update, but they are in an upgrade.
The reason is simple, an upgrade installs a completely new version of Windows, and then various settings are migrated from the old copy to the new copy. Microsoft doesn't have every setting configured to migrate, so in those cases the defaults remain because that's what they were when the new copy was installed.
If you're that concerned about these settings, file a bug report that those settings are not migrated to the new build.
Regardless, this is not a case of MS deliberately overwriting your settings, it's a case of them not having programmed the upgrade process to migrate them (yet).
here's another nightmare on this latest release..
I've tried to run and installed Chrome Browser, and Opera browser; they both install, look like they will run fine but neither one will actually open up!
Plus, of course, the wonderful Edge browser will open up for a second, but then immediately close itself..
I gotta say this release has more issues for me, than the last 10 releases did combined...very disappointed at this point..