New
#11
The pronoun "It" refers to the following sentence:
The output is not shown on a single line.
In the following reply (my post #7):
Windows 10 20h2 no longer upates
Windows 10 20h2 no longer upates
-
-
New #12
In which case, my answer is still valid:
Of course it was there originally, otherwise I couldn't have seen it in the editor when quoting you. I wrote that it did not appear (= was not displayed) before I quoted you.Crazy enough, the your sentence in bold did only appear in my editor when I "quoted" it, but not in your original reply (!?)
-
New #13
-
New #14
Hello @dalchina I thought I'd give you an update as I finally could find a time slot to proceed with your recommended procedure to recover my weird situation to something more normal. Long story short : yay, it worked, with a weird result tho. ^_^
So, I downloaded the latest Win 10 install software from Microsoft site and flashed it to a USB, booted from it and did a reinstall from scratch, after removing all partitions on the SSD. That worked out fine and the PC booted fine and well.
The reinstallation recreated the entry in the 'boot' tab of msconfig.exe as shown here (it was all empty before the reinstall, like it didn't know where the Active partition was ?):
And the reagentc /info command returned this output instead of an error:
In other words, there was again a boot store to be found and queried (I have no clue how it was even starting up before that), as the bcdedit command would also show now:
The weird thing is, when I peek into the diskmgmt.msc view I see this :
In other words, the same number of partitions as before, of same type and even the same size !
What the heck was actually wrong in the first place and how could Windows not correct that especially taking into consideration that it would effectively start-up !? Looks like it was "just" the matter of pointing at where that boot store was actually located and record it where needed ?
I'm speechless, tbh. Any pointers ?
-
New #15
Hi, you clearly had a partition issue or two initially, and you mention making changes related to your partitions. Quite how or what was missing or misplaced I'm not going to try to deduce.
Disk management does not show the smallest of the 4 partitions typical of a UEFI installation. Note you mentionbut not that one.after having moved the OS and EFI partitions to the SSD.
As regards the Recovery partition, it's quite possible- common indeed- for there to be one of more Recovery partitions present, but disassociated from the O/S (-> result 'disabled').
It would have been possible to sort out the partitions by technical means, but this would have been more complex and error-prone. The procedure I suggested was highly likely to result in success provided your Windows partition was sound, and a series of routine steps.
Quote
Related Discussions
