F5F Stay Refreshed Software Operating Systems Identify the issue: 0x800F018F error

Identify the issue: 0x800F018F error

Identify the issue: 0x800F018F error

R
Rattatta
Junior Member
8
02-01-2016, 12:20 AM
#1
I'm currently performing this task.
R
Rattatta
02-01-2016, 12:20 AM #1

I'm currently performing this task.

S
smarthead911
Junior Member
45
02-02-2016, 01:50 PM
#2
Failed to execute.
S
smarthead911
02-02-2016, 01:50 PM #2

Failed to execute.

R
Ryugoo
Member
93
02-03-2016, 10:42 AM
#3
This Reddit discussion highlights some interesting points.
R
Ryugoo
02-03-2016, 10:42 AM #3

This Reddit discussion highlights some interesting points.

I
iSenpaiKitty
Member
197
02-19-2016, 01:25 AM
#4
The .NET installation problems seem unrelated to your specific issue. The code 0x800F018F appears in both installers, and it looks like you're addressing two separate errors—0x800F081F and 0x800F018F—each with different causes. Make sure Event Viewer or Reliability Monitor can offer more details; it should appear under Application in Windows Logs in Event Viewer. Your current error is 0x800F018F.
I
iSenpaiKitty
02-19-2016, 01:25 AM #4

The .NET installation problems seem unrelated to your specific issue. The code 0x800F018F appears in both installers, and it looks like you're addressing two separate errors—0x800F081F and 0x800F018F—each with different causes. Make sure Event Viewer or Reliability Monitor can offer more details; it should appear under Application in Windows Logs in Event Viewer. Your current error is 0x800F018F.

Z
Zeeeus_PvP
Member
156
02-20-2016, 06:25 AM
#5
I understand, but all OP links showed 81F, not 18F. It seems like the mistake might have been copied incorrectly, which is typical with Microsoft issues.
Z
Zeeeus_PvP
02-20-2016, 06:25 AM #5

I understand, but all OP links showed 81F, not 18F. It seems like the mistake might have been copied incorrectly, which is typical with Microsoft issues.

M
Muffen_Man
Member
59
02-25-2016, 10:22 PM
#6
This might be accurate, since 0x800f018f appears to be an issue from when Vista x86 SP2 was still available. It seems Google is updating search results for that error to 0x800F081F, so keep that in mind. This code could be a revived problem from the Vista era or it might refer to something else.
M
Muffen_Man
02-25-2016, 10:22 PM #6

This might be accurate, since 0x800f018f appears to be an issue from when Vista x86 SP2 was still available. It seems Google is updating search results for that error to 0x800F081F, so keep that in mind. This code could be a revived problem from the Vista era or it might refer to something else.

I
iLoveUrte
Junior Member
7
02-26-2016, 04:58 AM
#7
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
I
iLoveUrte
02-26-2016, 04:58 AM #7

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

K
kervinc
Posting Freak
804
02-28-2016, 02:39 PM
#8
Your feedback seems unclear. It appears you're unsure between 18 and 81, and the affected PC isn't responding. Could you clarify?
K
kervinc
02-28-2016, 02:39 PM #8

Your feedback seems unclear. It appears you're unsure between 18 and 81, and the affected PC isn't responding. Could you clarify?

Y
YouriiruoY
Member
212
03-20-2016, 07:27 AM
#9
Sure, I understand. The number is 81, and it doesn't seem to matter.
Y
YouriiruoY
03-20-2016, 07:27 AM #9

Sure, I understand. The number is 81, and it doesn't seem to matter.

V
Venpirman
Member
219
03-22-2016, 12:49 PM
#10
Failed to execute.
V
Venpirman
03-22-2016, 12:49 PM #10

Failed to execute.