Solved .Net Framework problem. Can't update or install

[larryfoster]

I think I might have run the dism program.
Not sure.

A window popped up for a second and closed.
Tried to install 4.7.2 and got a fatal error

 

[iko22]

The DISM should be installed update. You can access it by opening an elevated command prompt window and then typing DISM /Online /Cleanup-Image.

If the computer cannot find DISM then check your Updates for KB3006137 . If needed you can download and install that update from here: fix windows update errors by using the dism or system update readiness

 

[larryfoster]

How do I o[en an elevated command prompt?

Thanks for your patience

 

[larryfoster]

Sorry to be so dumb.
I downloaded from the link and installed it but I don't know where to look for it or how to open an elevated command prompt

 

[larryfoster]

I just ran the DISM /online /cleanup-image

Got error 87
Attaching logs

Thanks for your patient help

 

[torchwood]

Hi Larry,

Dism doesnt play well with W7.

please run KB947821 (SURT)
https://www.microsoft.com/en-us/download/confirmation.aspx?id=20858


Roy

edited kb no:

 

[larryfoster]

Thanks, torchwood.
Downloading now

 

[larryfoster]

Well, installed the system update readiness tool and then tried to install 4.7.2 and it failed

 

[torchwood]

Hi Larry,

can i see the results of that KB (SURT)

copy/paste the results.

its in C >> Windows >> Logs >> CBS ... SURT.

might also be handy to run sfc /scannow.


Roy

 

[iko22]

Hello larryfoster, sorry to leave you high and dry - I'd been might busy today.

Anyway, regarding posts #25 and #24. Looking at this one explains the other. Error 87 is because DISM /online /cleanup-image was not run from an elevated command prompt.

An elevated command prompt is also called an administrators command prompt. You get this by running the command as an administrator.

To run cmd.exe as an administrator, open Start Menu, in search box, type cmd. When cmd shows in search results, select it with right-mouse click, and then select Run as administrator from the dropdown list. Input admin password if necessary, when prompted.

When the administrators command prompt window has opened, re-type DISM /Online /Cleanup-Image and run the command again. See what results you get.

 

[larryfoster]

iko22, no apology necessary.
I appreciate everyone's generous, patient help

After I posted I figured it out and ran it properly.

I had run sfc /scannow now a little earlier today.
I learned that I should also run it at an elevated command prompt.

Her is the log


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2019-01-29 12:36

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_59c2da0f1885c40e amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_none_59c2da0f1885c40e
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_519156f4ce47da7b amd64_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_none_519156f4ce47da7b
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_a17010e62d01ed14 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_none_a17010e62d01ed14
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_993e8dcbe2c40381 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_none_993e8dcbe2c40381
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_a65012d829d61c47 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_none_a65012d829d61c47
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_4cb15502d173ab48 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_none_4cb15502d173ab48
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_5ea2dc011559f341 amd64_avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_none_5ea2dc011559f341
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_945e8bd9e5efd44e x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_none_945e8bd9e5efd44e

Summary:
Seconds executed: 2635
Found 8 errors
CSI C Mark Deployment Not Marked Total count: 8

 

[torchwood]

Hi Larry,

Those errors are pretty standard, they all relate to Avast and DO NOT affect your system in any way..


Your best bet is a repair install. NO LOSS OF >>YOUR<< DATA.

Repair Install

Getting hold of a W7 SP1 ISO is not a problem.


Roy

 

[larryfoster]

I'll admit, it makes me nervous.

I have a lot of stuff on this computer

 

[torchwood]

Hi Larry,

to be expected, back up your OS beforehand using Macrium (free)
Imaging with free Macrium

Roy

 

[larryfoster]

Thanks for all your help.
It may be a day or two but will report back

 

[larryfoster]

Just wanted to report back that the issue has FINALLY been fixed.

I had continued to look for a solution short of installing Windows again.

That made really nervous.

I stumbled on to something called Reimage.

After checking it out, I figured the second worst thing was that it wouldn't work and I'd ask for a refund.
(Worst was it would crash my computer)

I tried it and it fixed a lot of things including my .net framework problem.

I want to thank you all and appreciate all your patient help.