Windows 10 Insider Preview Fast Build 19587.1000 - March 18 Insider

AndreTen said:

Fix it? most probably, you don't... MS will in one of the next build

Many years ago Windows 7 had exactly the same error and the solution was very simple, it was just to change permission on the "MachineKeys" folder.

So, I fixed mine but this one seems to be something else/more even though the error code is the same as the Windows 7 then.

Getting the same error here.




It's not causing any problems so I'll probably just see what happens after the next update.

meebers said:

I have the same errors in my event viewer, (no pop ups) tried to scroll down and locked event viewer. Next I went to

C:\Windows\System32\Microsoft\Crypto\RSA\MachineKeys to view settings. Mine is empty, both on production machine and the insider machine.

Mine is empty too so, I'm leaving it alone and see if the next update get rid of it.

- - - Updated - - -

DooGie said:

Getting the same error here.




It's not causing any problems so I'll probably just see what happens after the next update.

Hey guys I did a dism restore health and it keeps giving me a error message at 84% saying component not found check the log
start component cleanup and reset base work like usual.

Steven Campoli said:

Hey guys I did a dism restore health and it keeps giving me a error message at 84% saying component not found check the log
start component cleanup and reset base work like usual.

Hello Steven,

Unfortunately, this is still a known issue in the Insider fast builds.

We’re looking into reports where, when running corruption repair (DISM), the process will stop at 84.9%.

If needed, you could still do a repair install of Windows 10 instead.

Repair Install Windows 10 with an In-place Upgrade

Brink said:

Hello Steven,

Unfortunately, this is still a known issue in the Insider fast builds.



If needed, you could still do a repair install of Windows 10 instead.

Repair Install Windows 10 with an In-place Upgrade

Thanks I didn’t know U once again saved me a fresh install lol

No problem updating the host. I'm working with 2 VMware VMs and 1 HYPER-V VM. Looks like everything will work out.

Brink said:

Hello Steven,

Unfortunately, this is still a known issue in the Insider fast builds.



If needed, you could still do a repair install of Windows 10 instead.

Repair Install Windows 10 with an In-place Upgrade

Won’t need to repair, I usually run the start component cleanup, reset base and restore health after every build, their all ok 100% except for restore health so I know it’s not my machine since u said it’s a known issues for insiders in the fast build. Thanks again.