[SOLVED] Win10: Your device is missing important security and quality fixes

[imidazol97]

I may have a working repair going. This time it has spent over 30 minutes so far on updates that it checks for
before going into the repair mode. The other attempts did not do that.

It is now "installing Windows 10" using an ISO image on the computer's
hard drive and Mounted as drive F, so it shows up as just another hard
drive of its own.

If this is successful, details when it's finished as to if it solves the
problem in the title about Windows Update.

 

[imidazol97]

Windows to GO was the key! The computer thought my SSD was an external usb.
I had searched for connections of my title problem with Windows to Go.

Today after you mentioned Windows to Go could be something I did wrong or I was downloading
wrong version, I went searching for Windows to GO and external USB and can't repair Windows10.

Found Microsoft topic that helped. I tried both and the registray fix changing the value from 1 to 0
allowed me to use my Mounted copy of Windows.iso per directions and it started downloading
updates in prep for repairing!!!. AND it has worked.

After a couple or 3 hours on DSL 3.5Mbps my error in the title of the topic if GONE.
Windows Update even downloaded a .net preview update

I will watch to see if Windows Update works correctly now as new updates are
released for this laptop.

 

[x BlueRobot]

Found Microsoft topic that helped. I tried both and the registray fix changing the value from 1 to 0
allowed me to use my Mounted copy of Windows.iso per directions and it started downloading
updates in prep for repairing!!!. AND it has worked.

Could you please provide the link to the topic you read? It'll be interesting to see what you did to get it working, others may experience the same issue in the future and it may be helpful for them too.

After a couple or 3 hours on DSL 3.5Mbps my error in the title of the topic if GONE.
Windows Update even downloaded a .net preview update

I will watch to see if Windows Update works correctly now as new updates are
released for this laptop.

That's great news, so you've managed to also update to the latest Windows build too?

 

[imidazol97]

The Windows to Go problem is what I searched for. I found this answers.Microsoft.com topic.

https://answers.microsoft.com/en-us...and-cant/1faafbab-00f8-4ddb-91e0-6720ffee7b3f

I used the registry edit after exporting my current registry first for backup.

I changed the value rather than deleting the portion of the registry line as suggested at first.
This suggestion was in one of the answers that you have to click the down arrow to see.

MichaelDiPasquale says.
"Thanks! This solved my issue. I actually ended up changing the value in PortableOperatingSystem from 1 to 0 instead of deleting"

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
Then in the right pane if this value exists - PortableOperatingSystem
Right click and delete it.

I changed value to "0"

This fixed the problem of not being able to do any repair with a new copy of
Windows 10 using Windows Creation Tool. This allowed me to apply the windows.iso
I had already downloaded but like the other attempts to repair my Windows 10
quit saying it couldn't be used to repair Windows on an external USB, which is
back to the Windows to Go symptom that popped up on restarts earlier.

Using the Windows.iso which I had downloaded and then mounted per the directions on the

Download Windows 10

site and others about mounting the iso as a drive without making a DVD.

It started downloading updates before it actually ran to repair the Win10!
The new copy of Windows fixed the Updates error. IIRC, after changing
the registry I rebooted and looked at Windows Update and it still showed
the error in the title of this topic.

Today Win Update found an Office update and installed it! I think we're FIXED!
Thank you.

 

[x BlueRobot]

Thanks for providing the thread you read and I'm glad your issue appears to be resolved now, hopefully you won't have any additional issues in the future. I'll mark this thread as solved for now.