Win10 Fall Creators Update from A to Zzzzzzzz

Topic

New Reply

Preston Gralla hits it out of the ballpark again. His review of the next version of Windows, known as the Fall-in-North-America Creators Update, versi
[See the full post at: Win10 Fall Creators Update from A to Zzzzzzzz]

Reply | Quote

Replies

Remember, Windows OS upgrades used to come about once in 3 years (eg from Win 7 to Win 8) which was decent enough wrt new features and MS were making decent profits from the sales of new Windows licenses every 3 years.

To fulfill their greed for more profitS, MS have greatly shortened the Win 10 upgrade cycle to about twice a year. That’s a huge change from once in 3 years to twice a year. Hence, the new features in each Win 10 upgrade are zzzzzzz and the short upgrade cycle resulted in much instability in Win 10, like an epileptic suffering seizures every 6 months.

Most businesses preferred the Windows upgrade cycle to be nearer to once-in-10-years, eg about once in 6 years, so as to maintain stability in their business operations and to save on costs = less profits for MS.

2 users thanked author for this post.

lurks about, Elly

Reply | Quote

The only immediate change to Windows 10 I want to see is having the LTSB version in stores.

There are many other changes after that.

 

 

3 users thanked author for this post.

HiFlyer, woody, Elly

Reply | Quote

And also an option for Home users to switch to the LTSB effortlessly. Right now I’m being forced to upgrade just so I can keep getting security patches, not that I actually care for 90% of the stuff MS does in their Windows 10 “upgrades”.

Reply | Quote

I just ran into an issue that I managed to resolve and hopefully putting it here can help others.

I run a dual boot of Windows 7 Ultimate 64 bit and Windows 10 Pro 64 bit. I use Windows 7 as my main for everything and only use Win 10 as a test system and usually have to choose which OS I want from the traditional DOS like menu after post. I do this so I can poke, prod and dissect Win 10 like the unholy creation it is without fear of losing my PC to a mistake. Since 1709 is coming out tomorrow I decided to finally update my Win 10 to 1703 from 1609. I keep both OS’s on physically separate drives for an extra measure of safety.

To my surprise after Win 10 upgraded/updated/whatever M$ is calling it these days it immediately booted straight into Windows 10 without giving me the option to choose. To say I was miffed was an understatement. So righteously I went to the BIOS and disabled the SATA controller that had Win 10 on it. Rebooted and I was met with a high res blue screen with giving me an error code of ‘0X000000e’ with options on it, which included “use another Operating System” which I used and it started to boot Windows 7. It then wanted to do a Disk Check before booting. It booted into Windows 7 no problem and everything worked. Except every time I rebooted the PC it would go through the same process.

Eventually I re-enabled the sata drive in the BIOS and Windows 10 would automatically boot. I figured I would try different things and eventually I found something that worked.

When Windows 10 Started to boot I pressed F8 and it brought me to another high res blue screen which gave me more options. I saw an option that showed the “default OS” as Windows 10, I clicked on it and was able to change it to Windows 7. Now every time I restart the PC it automatically goes into Windows 7 and not Windows 10. So no more easy and quick menu to choose which OS you want but a convoluted one they forced on people in hopes they would not figure it out and just use the default.

So upgrading Windows 10 from 1609 to 1703 changed my MBR without my permission they just did it anyway without telling me about it. Thankfully I have things working the way I want it to “mostly” but I have even less respect for M$ now. They need to get their act together, actually get a clue as to how they are treating their customers and the disrespect they are showing them.

I mean come on, how hard is it to give a warning when “upgrading” to give a message that if you are dual booting, this is what you need to know because, you know we changed things…again.

Rock

2 users thanked author for this post.

HiFlyer, Cybertooth

Reply | Quote

Can you run plop boot manager on that system? Might help with next upgrade…

Reply | Quote

@ Rock

I think what happened to your computer is normal for a multi-boot system, ie the last OS installed will take-over booting of the MBR(= for a Legacy BIOS install) and becomes the default OS.

Initially, when you dual-booted Win 10 1607 with Win 7, you had likely installed Win 10 1607 first and then Win 7. In this case, Win 7, being the last installed OS, took over booting of the MBR and became the default OS.

Upgrading Win 10 from 1607 to 1703 is the same as installing a new OS. So, when you installed/upgraded Win 10 1703, it took over booting of the MBR from Win 7 and became the default OS.
… So, to reinstate the MBR configuration with Win 7 as the default OS, you may need to also reinstall Win 7 as the last OS.

Bear in mind that the many reinstalling and/or Win 10 upgrading in your dual-boot system will eventually fill up the tiny MBR partition = computer may become unbootable = requires a complete clean reinstall of both OS.

This does not disprove the fact that certain Windows updates have borked a multi-booted system.

P S – I am not trying to defend M$ but just stating the truth about multi-boot systems.

The EasyBCD program can be used to edit or repair the MBR of Windows computers. EasyBCD does not work for modern UEFI Win 8.x/10 computers.

Reply | Quote

@ Rock

… continue ….

To eliminate the problem, likely you can opt to install Win 7 and Win 10 with the other internal hard-drive unplugged. In this way, each separate drive has its own MBR partition and booting will be through BIOS setup and not through a DOS menu after POST.
… Thereafter, whenever Win 10 needs to be upgraded, unplug the Win 7 hard-drive. After the Win 10 upgrade has completed, replug the Win 7 hard-drive.

Reply | Quote

From Windows 10, version 1709 enhanced telemetry events and fields used by Windows Analytics: ‘In Windows 10, version 1709, we introduce a new feature: “Limit Enhanced diagnostic data to the minimum required by Windows Analytics”. When enabled, this feature limits the operating system telemetry events included in the Enhanced level to only those described below. Note that the Enhanced level also includes limited crash reports, which are not described below. For more information on the Enhanced level, see Configure Windows telemetry in your organization.’

Reply | Quote

There are 6 security-related blog posts from Microsoft today at https://blogs.technet.microsoft.com/mmpc/.

Reply | Quote