Author Topic: .net4.8: 0x800f0922; Firefox: 0xc0000022 (Read 12731 times)

George · « **on:** June 03, 2019, 11:14:53 pm »

Hi,

I've tried to install .net4.8 but failed with error 0x800f0922

Also, recently Firefox wouldn't start with error 0xc0000022

Are these related, how to fix it?

I run Windows 8.1 64 bit; other programs, including browsers, work fine.

Thanks a lot.

Boggin · « **Reply #1 on:** June 04, 2019, 12:33:45 am »

It could be related but have a look through this article on how to troubleshoot Firefox.

https://support.mozilla.org/en-US/kb/firefox-wont-start-find-solutions?redirectlocale=en-US&redirectslug=Firefox+will+not+start

My first thought though would be to uninstall it and download afresh.

As for the Windows Update failure, this article has some suggestions for that error code.

https://windowsreport.com/windows-update-error-0x800f0922/

George · « **Reply #2 on:** June 04, 2019, 01:18:50 am »

Thanks, I've tried some of the suggestions in these articles, gonna try the rest.

Boggin · « **Reply #3 on:** June 04, 2019, 01:29:59 am »

There are a couple of cmds that can resolve update problems in Win 10 which may also apply to Win 8.1

These are run from a Command Prompt (Admin) and are -

dism /online /cleanup-image /startcomponentcleanup

dism /online /cleanup-image /restorehealth

and then enter sfc /scannow to see if any corruption remains.

These each will take a while to run.

George · « **Reply #4 on:** June 04, 2019, 01:50:45 am »

Yes, I've tried these.
sfc /scannow said it had found some corrupted files but couldn't fix all of them.
dism /online /cleanup-image /restorehealth said that the source wasn't available.

Boggin · « **Reply #5 on:** June 04, 2019, 01:53:25 am »

Can you run another sfc /scannow and when it reports the same, download and run SFCFix.exe and post its report.

https://www.majorgeeks.com/files/details/sfcfix.html

George · « **Reply #6 on:** June 04, 2019, 02:10:37 am »

Thanks, I will do that.

George · « **Reply #7 on:** June 04, 2019, 03:18:18 am »

Weirdo, isn't it?

Boggin · « **Reply #8 on:** June 04, 2019, 03:20:10 am »

Okay - can you now download and run SFCFix.exe and post its report.

Boggin · « **Reply #9 on:** June 04, 2019, 03:52:24 am »

I'm going offline shortly for 3 - 4hrs but will be back later to see how you are getting on.

George · « **Reply #10 on:** June 04, 2019, 04:52:29 am »

Didn't you mean the SFCFix.txt that I've posted already?

Boggin · « **Reply #11 on:** June 04, 2019, 08:15:54 am »

No - that is what the sfc /scannow has reported.

You need to download SFCFix.exe from the link I'd posted in my earlier reply.

This needs to be run straight after a sfc /scannow as a CBS log can be volatile.

This is why I asked you to run another sfc /scannow so that the CBS log it produced would be fresh.

You will need to run another sfc /scannow and then download that program and run it.

That will produce its own report as to what it could or couldn't fix and what I want you to post.

George · « **Reply #12 on:** June 04, 2019, 08:43:30 am »

Oh, I did so but not immediately after sfc /scannow. I thought that the SFCFix.txt, which did say no corruption, was the result.

All right next time I run the two right after each other. Do I need to download again, can't run the previous copy?

Boggin · « **Reply #13 on:** June 04, 2019, 08:51:43 am »

If you've already run SFCFix.exe it should have put a log onto your computer - can you dig it out and post it.

If it has already repaired what sfc /scannow couldn't then it will have that in its report, but to confirm, run another sfc /scannow which should report no integrity violations.

If that is the case, then try Windows Update again.

Another run of SFCFix.exe on a fully repaired sfc would produce a no error SFCFix.exe log.

George · « **Reply #14 on:** June 05, 2019, 03:48:27 am »

I ran SFCFix right after sfc /scannow as you said. It ran very long and then started DISM which ran even longer.
The end note of SFCFix and DISM log are enclosed, I couldn't find any log of SFCFix.

Boggin · « **Reply #15 on:** June 05, 2019, 04:35:32 am »

I would have to run a sfc /scannow and then SFCFix.exe on my Win 7 machine to see if I could check to see where the SFCFix.exe log was but from your screenshot, it may not have completed a report.

It would take too long to perform this on my Win 10 machines.

In light of the corruption reported on your system, I think the best option now would be to perform a repair install which wouldn't affect your personal stuff or installed programs.

This article will walk you through how to do that for Win 8.1 - https://www.winhelp.us/non-destructive-reinstall-of-windows-8-and-8-1.html

If that doesn't resolve your problem then you may have to consider what I call the nuclear option of a Reset which can retain your personal stuff but would remove all 3rd party installed programs.

George · « **Reply #16 on:** June 05, 2019, 05:07:22 am »

One last question before I resort to such drastic measures. DISM says that the source can't be downloaded; isn't there any way to do that somehow?

Boggin · « **Reply #17 on:** June 05, 2019, 05:14:44 am »

This article has a number of suggestions on how to overcome that error (although I haven't read through them), but I think it would be better to opt for the repair install.

https://www.wintips.org/how-to-fix-dism-source-files-could-not-be-downloaded-0x800f0906-windows-10-8/

I have to shoot off for a while now but will be back.

George · « **Reply #18 on:** June 05, 2019, 05:17:02 am »

Thank you for all, I'll do what you said is left.

Boggin · « **Reply #19 on:** June 05, 2019, 08:05:28 am »

Let me know how you get on.

George · « **Reply #20 on:** June 06, 2019, 08:22:22 pm »

You noted that SFCFix.exe may not have completed, so I tried again. I let it run for 12 hours, the hyphen was still blinking but nothing else was shown after the DISM report that I posted. Does it mean anything to you?

Boggin · « **Reply #21 on:** June 07, 2019, 12:52:13 am »

It sounds like it's struggling because of the level of corruption and because the dism /restorehealth failed to run.

I'd go ahead with the repair install.