Help Diagnosing Error: 0x800F018F

[JustAStrangeGeek]

Hey Guys,

 

I have posted a thread about why this issue was happening on the LTT forums. Short answer, no luck there. So instead, I am creating a thread for help of the diagnosing stage of this error. 0x800F018F has been appearing every time I try to install 16299.192 (KB4056892), or the Windows meltdown patch. The error, when googled, shows that the error is of .NET Framework 3.5:

 

Quote

https://support.microsoft.com/en-us/help/2734782/net-framework-3-5-installation-error-0x800f0906-0x800f081f-0x800f0907

 

Error 0x800F018F

The source files could not be found. 
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

0x800F081F - CBS_E_SOURCE_MISSING

Error code: 0x800F081F

 

The thing is, other updates that are not 16299.192 install whereas the meltdown patch refuses to install. I have ran the Troubleshooter several times and have turned off my AV, no luck. I have ran the Command Prompt command 'DISM /Online /Cleanup-Image /RestoreHealth' and the command reports that there are no issues, I also ran command 'sfc /scannow' also reporting there being no issue.

 

Microsoft's fix:

Quote

Error code 0x800F0906, 0x800F081F, or 0x800F0907

To fix the error codes for Windows 10, follow these steps:

1. Download the Windows Media Creation tool, and create an ISO image locally, or create an image for the version of Windows that you have installed.
2. Configure the Group Policy as in Method 2, but also follow these steps:
   1. Mount the ISO image that's created in step 1.
   2. Point the "Alternate source file path" to the ISO sources\sxs folder from the ISO.
   3. Run the gpupdate /force command.
   4. Add the .Net framework feature.

I am running Win10 Home 64bit so Group Policy is out of the question meaning that this 'fix' will not apply to me. I really don't want to reset or reinstall windows and would prefer to write 10 hours of code in PowerShell to fix this issue. Anyone know how to diagnose the issue?

 

Thanks.

[JustAStrangeGeek]

Currently performing this:

Quote

By using DISM component cleanup switch, you can clean up the image and get everything running properly again. Here’s how to get it done.

1. Open the Start Menu, type cmd, right-click and Run as Administrator.
2. In the elevated command prompt, type the following commands in the same order:
   dism.exe /online /Cleanup-Image /StartComponentCleanup 
   sfc /scannow
3. Wait for these commands run and when they’re done, run:Dism /Online /Cleanup-Image /RestoreHealth

At this point, Dism /Online /Cleanup-Image /RestoreHealth should work again.

https://appuals.com/fix-dism-restorehealth-error-0x800f081f/

 

[JustAStrangeGeek]

7 minutes ago, JustAStrangeGeek said:

Currently performing this:

 

Didn't work.

[Tsuki]

check out this reddit thread

 

[PorkishPig]

.NET installation errors don't quite relate to the issue you're running into. The error code 0x800F018F just happens to be utilized in both installers. Additionally, it looks like you're following instructions to resolve 0x800F081F in two instances instead of 0x800F018F, which are two entirely different errors.

 

Check to see is Event Viewer or Reliability Monitor are able to provide any further information on the error. It should be under Application in Windows Logs in Event Viewer.

5 minutes ago, Tsuki said:

check out this reddit thread

OP's error is 0x800F018F.

[Tsuki]

1 minute ago, Homeless Pineapple said:

OP's error is 0x800F018F.

i know, but everything OP linked, was 81F, and nothing on microsofts website says 18F. so im guessing either OP typed it wrong, its its the same error(which common for microsoft errors)

[PorkishPig]

3 minutes ago, Tsuki said:

i know, but everything OP linked, was 81F, and nothing on microsofts website says 18F. so im guessing either OP typed it wrong, its its the same error(which common for microsoft errors)

This very well may be true, as 0x800f018f seems to be an error that occurred back when Vista x86 SP2 was still around. It does seem that Google is correcting 0x800F018F search results to 0x800F081F, just keep that in mind.

 

0x800f018f is either a resurrected error from the Vista age that is incredibly uncommon or an alias for another error.

 

https://answers.microsoft.com/en-us/windows/forum/windows_vista-update/vista-x86-sp2-wont-install-0x800f018f/08787f94-366f-4c92-8781-e3f308bf9e48

[Tsuki]

7 minutes ago, Homeless Pineapple said:

This very well may be true, as 0x800f018f seems to be an error that occurred back when Vista x86 SP2 was still around. It does seem that Google is correcting 0x800F018F search results to 0x800F081F, just keep that in mind.

 

0x800f018f is either a resurrected error from the Vista age that is incredibly uncommon or an alias for another error.

 

https://answers.microsoft.com/en-us/windows/forum/windows_vista-update/vista-x86-sp2-wont-install-0x800f018f/08787f94-366f-4c92-8781-e3f308bf9e48

that error only happened when installing Vista SP2.

Seeing as OP has Windows 10, that is not his issue, it wouldnt have been "resurrected".

 

Like i said, he either typed it wrong, or its the same as 0x800F081F.

 

and looking at other threads ive found, people have gotten the same error(18F) while trying to install openspan software on win10, with the same .net3.5 fix as 81F

 

ITS THE SAME ISSUE

[JustAStrangeGeek]

29 minutes ago, Tsuki said:that error only happened when installing Vista SP2.

Seeing as OP has Windows 10, that is not his issue, it wouldnt have been "resurrected".

 

Like i said, he either typed it wrong, or its the same as 0x800F081F.

 

and looking at other threads ive found, people have gotten the same error(18F) while trying to install openspan software on win10, with the same .net3.5 fix as 81F

 

ITS THE SAME ISSUE

Okay... Your comments are slightly confusing. My mind is racing on to which one it is, 18 or 81. The effected PC is currently off so I cannot tell.

[JustAStrangeGeek]

Sorry, I did spell it wrong. It's 81 not 18. But based on you guys, it seems not to matter?

[JustAStrangeGeek]

59 minutes ago, Tsuki said:

check out this reddit thread

I'll try the command and report back.

 

[JustAStrangeGeek]

Didn't work.