The despotic arrogance of Microsoft

MaloK said:

I think this does just start Internet explorer on top of Edge. It will probably not work without IExplore.

Could well be but the settings are there in Windows 11 and IE is removed.

I'm on Win 11 and this is what shows,

I also have what @Fabler2 said but I'd wonder if QuickBooks will get Edge to open if the "Reload in Internet Explorer mode" is set in Edge. Putting iexplore in the WinKey + R box does that on mine.

dorcom said:

Did all that, been there, done all that.
If it would work I would not be posting here!
Yes, I am frustrated.
I have a perfectly running machine, all hardware in perfect working order.
No malware, virus or else.
No issues no blue screen until that "update" which created a litany of errors, blue screens and issues included some disk errors that needed to be repaired.
-System thread exception not handled
-Bad system config info
-Kernel security check error
Attempting repairs...
Repairing SSD...
"We couldn't complete the updates..."

I don't have time for this nonsense considering that everything works perfect, until of course that update....
I need my time to do work to get paid and no free Microsoft troubleshooting.

Lastly if it where a user issue like some smart...es cynically "help" by insulting, mocking and ridiculing, (a character statement) then maybe they all have an answer why the web is full with:
"Windows updates KB5005033 fail to install" or "Cumulative update KB500503333 fails to install" etc. et al and practically all answers are the typical copy paste 7 steps of "No one really has a clue".
Same like here, spewing cynical ridicule blaming the user yet not knowing a shred of facts!
Never assume.

Sinccerely,

Like in this previous post (#38) as above mentioned I did the whole thing again on a perfectly running machine Microsoft pushing against their update .
(The one policy setup is the default of excluding drivers)

I checked everything on my system and found it to be 100% working conditions, CPU tests, memory test SSD test, virus free malware free root kit checked you name it, I did.
I did a clean boot (MSConfig) so only the essentials are running. Switched all startup apps off. Disconnected any USB devices that were not necessary. And rebooted again running a clean Windows 10 with only the essentials.

Then as per an M$ recommendation I started an in-place upgrade by refreshing Windows, leaving files and apps intact but prior to that, let it download any upgrades & updates. The machine churned away, rebooted and continued to rebooted and continued and then the bomb went off.
On the following reboot: "undoing changes made to your computer"
then fixing Drive C as like mentioned before it, trashes my drive C
then scanning and repairing drive C
then a blue screen "your device ran into a problem"
stop code "system thread exception not handled"
then I reboot another blue screen "recovery" 0xc000000f or -e stating that I need to use recovery tools but none of the function F1 or F8 escape did anything.
To add some extra fun on one occasion my bios was also thrashed and reset!
GREAT! Maybe it's gonna blow up or go up in flames too...

Crash after crash hard disk repair after hard disk repair...
Why is it trashing my hard disk?
Finally I got it back up and running with the message "we couldn't install Windows 10" we set your PC back to where it were right before you started...la la la.
I now understand how those pilots must've felt in the Boeing 737 Max when the MCAS system started to f... around with them nose diving the plane into the ground.

Once Windows managed to "resurrect" itself I get the final candy:
Error code 0XC1900101-0X40017 the installation failed in the second boot phase with an error during boot operation.
Oh how sweet, such a sophisticated operating system... This time kind enough not to say which error code.
The latter is likely the thrashing of the storage device.

Then another BSOD crash 0xc0000225,
F1 to "enter recovery environment" reboots...
the upon reboot 0xc000000f
then shuts down.
Now all is total trashed.
SSD data irreparable damaged.
System events logs shows several event IDs about NTFS file corruptions took place during the update/upgrade event.
Event ID 132, "too many repairs in a short time" Event ID 133 "Bad FRS "repairs and 55 "corruption discovered in the file system structure" etc and more like application errror backgroundtaskhost.exe, winstoreapp.exe event ID 1000,
I'll be happy to provide of the system event logs.

Wasting more time trying to find answers I came across the usual copy& paste variation on the theme of run-of-the-mill solutions including the infinite brilliance of reformatting hard disk and reinstalling Windows...
I do that with my house too! If the front door jams I tear down the whole house, dig a bigger hole, pour a new foundation and start from scratch building a new house...

Fortunately I do twice a week full C: partition backups and ended up "rebuilding the house" by restoring a previous backed up full partition...

So to all those who saw the need to complain to and belittle me, labeling it all an user error, do be so kind and give me a constructive suggestion and solution as to what it is that only otherwise perfectly harmoniously and error-free running system, KB 402-3057 and KB 500-5033 trash and corrupts the SSD and creates total havoc.
If I had not for the 4th time bother with these updates, everything would still be running fine and smooth with no error event IDs.
I will spend more time and research and I'm certain I will find something to proof that it is not "some user error" but some serious underlying issue, some defect that just like a disease, if the conditions are right, can kill. Just like covid does not affect some people but kills others.

Again, so do explain to me, Micro$oft or not, what is the problem here?
I know one thing for certain it ain't user error that some saw a need in making a mockery of.

Now the system is completely irrecoverably trashed and I have to install the full C: partition from a backup.

Looks like you need to replace the SSD and if any of those errors occur again, reseat the RAM sticks.

Then another BSOD crash 0xc0000225,
F1 to "enter recovery environment" reboots...
the upon reboot 0xc000000f

Those are not BSODs, FYI, IIRC: (not even stop codes) (looks like failure before the kernel loads)