"We couldn't update the system reserved partition" failure build 1903

That's probably the way ahead, but still a hassle. If only I could get a way to generate a C: prompt, I would try yet something else.
Never forget: it's the update that caused all the trouble. First by making my external hard drive unreadable (the contents of which I fortunately could recuperate by going back via rollback to a state before the update inception - absolute proof that it was the update, which was the culprit - and still is).
But, as said, I'm not the only one.
Any thanks anyway.
Haku

dalchina said:

Told you how..

I don't think he is reading our posts.

So, what did you say? Please repeat.

Find a camera or smartphone camera to take pictures an post images into the thread.
In case there are problems posting images please post share links using one drive, drop box, or google drive.

1) Find 3 flash drives that you can format (> or = 8 GB) (some or all may be used)

2) On a working computer create tools to use to backup files and for troubleshooting:

a) Bootable Windows 10 iso:
https://www.microsoft.com/en-us/soft...load/windows10

b) Kyhi boot rescue:
Toolkit Item: Kyhi’s Rescue Disk – Win10.Guru

c) Bootable Ubuntu flash drive:
Create a bootable USB stick on Windows | Ubuntu tutorials

Post images of the steps / results as per NavyLCDR and dalchina's posts (#27 and #29).

If all troubleshooting steps fail plan to:

a) backup important files > clean install
or
b) perform a reset save files equivalent (reinstall drivers and applications)

Hi!
Some good news, some same news.
First, I do read your threads carefully. But some of them are a bit above my experience capabilities - or the explanations and suggestions do expect such foreknowledge on the part of the reader, that they are either very difficult to grasp, or not at all. Be all that as it may, the latest post by NavyLCDR produced some welcome results.

The third possibility (Ubuntu) did not help me a lot because for some reason Rufus kept failing at some point when transcribing files.
On the other hand, Rufus worked perfectly when setting up Kyhi, and allowed me to recuperate all still missing files that hadn't been backed up.
Tiny drawbacks when using Kyhi:
- The screen has a safe mode resolution. Unfortunately, on my monitor(s) in that resolution one can't see the whole screen (see attached pic). Display drivers are not provided, so one can't change this.
- Second, Kyhi is geared to a QWERTY keyboard - and no way to change this (we use AZERTY over here).
But these are very small problems, compared to the advantages of that recovery tool, many of which I have to explore yet.
So, now I am set to do a clean install - for the 3rd time in the sad evolution of Windows 10.

Yet, I wonder: As you know (re)installation of Windows from an exterior medium like a UFD does not permit re-installation while preserving one's elements (option 1) but obliges the user to do a clean install (option 2) - but apparently a re-installation from an ISO file on the computer, would allow option 1... would it not be an idea to download the ISO file while the computer is in its Kyhi fase, so to speak? But maybe that is a pipe dream, since starting up via Kyhi changes the letters of the drives, because the recovery takes over letters C: and D: (in fact of all the partitions of the basic disc)...

So, I'm all set to do that clean install. But this means that Microsoft once again managed to oblige me to go through a clean install all over (which includes re-installing lots and lots of application, not to mention the fine-tweaking of my machine). I am not into conspiracy theories, but I begin to wonder there too.
As I was safely doing the backups and mirrors via Kyhi (which proves by the way that nothing is wrong with the main hard disk!), I just checked for fun all the logs and panther files. And what do you know: just some time before I got my BSDO misery (see previous messages), Microsoft had sent yet another one of their 1903 updates, and this despite I had taken every precaution that this should not occur. And the update was aborted by what occasioned the BSOD. I find this highly suspicious...

One last thing: I attempted a repair of the system after an error code 0xc000000f (which was the reason for the BSOD) as proposed by Microsoft in their page:
https://answers.microsoft.com/en-us/...f-2f0ec14b0e6c
But as I expected, it did not work. I think it is perhaps because Kyhi changes the partition letters. I don't know.

So thanks to all.

I can at least start working properly again.

Not closing the thread yet. But will do that as soon as Windows has been re-installed.

haku

Kyhi boot rescue uses Windows enterprise.

When in Windows Recovery Environment (RE) it is common for drive letters to change.
Once a computer is repaired and Windows is again available the drive letters return to the typical drive letters.

Options are:
clean install
reset save files equivalent (performed using the bootable windows 10 iso)
troubleshoot

When installing drivers make sure that they are from the computer or motherboard manufacturer's websites.
For any drivers needed that are not displayed use the component manufacturer's websites: Intel, Nvidia, AMD, Killer Networks, Realtek, etc.

Once you have installed drivers, applications, files, etc. make a backup image and save the image to another disk drive or the cloud.
(Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.)
There are free and pay versions depending on the features.

Macrium is widely used in Ten Forums:
Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect

Thanks for the latest handholding!

Addenda to my previous message: I managed to start Ubuntu finally. Looks nifty but not as useful as Kyhi.

Macrium was present on kyhi. Saw one can make images / mirrors with it. But it had also a boot repair. Tried it, but didn't help. What's so upsetting in my situation is that everything works, all disks and partitions are healthy, Windows boots perfectly until after password input. Then: normal activity including aero, then as it has to switch to the desktop: black screen. Complete mystery for me. But what's no mystery: mishap happened as Windows was making another attempt at updating to 1903. Very frustrating.

haku

Black screens are typically GPU related.

Ubuntu can be used to backup files and to test hardware.

zbook said:

Black screens are typically GPU related.]
Indeed. Except that here the GPU seems to function perfectly since it shows the wallpaper photo on the lock screen without any problem in full HD. It must be something else. If it can render that lock screen image on the display, I don't see why the GPU wouldn't be able to display the rest. Anyway, all graphics of all kinds function in Ubuntu. Linux is somewhat different than Windows, but when it comes to the display, I don't think that different.
As I can demonstrate, it's again that update which is at fault, I'm absolutely certain of this. Too many coïncidences again this time.

But it'll soon be moot since I've had enough trying to get the thing going without a clean re-install. But it remains frustrating not to be able to counter the Microsoft update shenanigans. We've tried out best, but the spaghetti programmation has gotten the better of us. Of me anyway.

H
[Ubuntu can be used to backup files and to test hardware.

Since I got Ubuntu finally working, and found it useful indeed, I installed it alongside Windows (took some doing coz the first time around I was confronted with a grub rescue - got out of that with a second install).

Never been so long at my computer without being productive in my real work!

But I keep being grateful for your continuing help. Still, please remember what concerns explanations: you are not always addressing people who know what you know...

haku