By right your friend have 2 options. If the previous w10 was activated successfully, and no hardware changes were done, your friend should be able to do a clean install of w10 and get it activated automatically online. MS server should have collected the information about his computer and hence the online activation should be working. I can confirm this one works because i just did a clean install on my computer yesterday and it got activated when it was online. Automatically.

Another one is to revert to old os, and call ms directly for help.

Like i said before, recovery options depend on what you have done to prepare for the worst. The more efforts you put in, the more choices you have. If you don't do it at all, your options are limited.

not sure, but imo it should start when ms server has collected the hardware id of your computer during a successful upgrade. (which means last Friday)

as long as you do the downgrade within the 30-day period, it should be fine.

restart ur pc & re-run sfc /scannow

don't worried too much.

m'sia common use WD & Seagate. my personal exp, too many failed toshiba hdd on my side.

HGST also good.

My start menu is not working. 

Latest announcement

Announced today that about Windows 10 Redstone -  successor to Windows Threshold and is expected to arrive next year in two waves similar to TH1 and TH2, the two waves we have seen builds from this year.

Now it seems that Build 11082, the most recent Windows 10 Redstone build seen on Buildfeed, may be under testing for Windows 10 Mobile too.

The Build 11082 is mentioned as “10.0.11082.1000.rs1_release.151210-2021”.

Also known as RS1 corresponds to Redstone 1, the first phase of Windows Redstone.

from that link, it appears that it doesn't impact system stability in general. imo this is a chicken and egg thing. at one side, ms tries to enforce system integration checks on everything, including drivers, to ensure better system stability. on the other hand, this system checks are kind of hard to implement for things like drivers, especially that are always in active development-release cycles.

for now i think you can safely ignore it.
i think there must be some sort of logs that tells you what happened.

i personally never install spendid in my old g55. the machine and software works fine without it.

yes. you should have found out for now because if you click on the link and proceed with the steps, you will get to see the isos are named as Win10_1511_English_x32 or Win10_1511_English_x64.iso (which are essentially meaning 10586)

how did you run your iso file?

you can verify if the iso has the correct checksums:

1. download Microsoft File Checksum Integrity Verifier, https://www.microsoft.com/en-us/download/de...s.aspx?id=11533
2. select the file and right click to extract the files in a folder (eg. with 7zip/winrar). the program you need is called fciv.exe
3. put fciv.exe and your iso in the same directory
4. press shift key + right click in that directory in file explorer, and from the popup select 'open command windows here'
5. type fciv -md5 iso.filename and press enter key. wait until the calculation completes, the md5 checksum for your iso file will appear
6. compare it with the following:

91fad72bb84ee259cdb1772b2ce42375 *w10_1511_en_x32.iso
a0d4271b7537732a060909fd39d54829 *w10_1511_en_x64.iso

if it matches, your iso file is good. if not, download again.

how did you run your iso file?

you can verify if the iso has the correct checksums:

1. download Microsoft File Checksum Integrity Verifier, https://www.microsoft.com/en-us/download/de...s.aspx?id=11533
2. select the file and right click to extract the files in a folder (eg. with 7zip/winrar). the program you need is called fciv.exe
3. put fciv.exe and your iso in the same directory
4. press shift key + right click in that directory in file explorer, and from the popup select 'open command windows here'
5. type fciv -md5 iso.filename and press enter key. wait until the calculation completes, the md5 checksum for your iso file will appear
6. compare it with the following:

91fad72bb84ee259cdb1772b2ce42375 *w10_1511_en_x32.iso
a0d4271b7537732a060909fd39d54829 *w10_1511_en_x64.iso

if it matches, your iso file is good. if not, download again.