Windows Explorer restarts when I try to view 'Computer' properties

This just started the other day, and I can't figure out what the issue is

I click on the start button, and then right click on Computer, and select Properties.

The Control Panel main screen comes up for just a second, and then closes and Windows Explorer restarts.

The computer itself does not reboot. The desktop just goes away and comes back, as if the computer has rebooted.

I have run Malwarebytes and a Virus Scan on the computer, as well as a bunch of other tools and diagnostics. Found no problems.

I am currently running a quad core AMD A8 processor and Windows 7, with 8 GB of ram.

Confusing.

Link goes to a small video clip on You Tube of the problem in action.
https://youtu.be/iMyK0Ox5QQU


Anyone have any ideas?

I actually had considered that. In looking at my restore points, I only have a few and they are mostly after I found the problem, so no help. I do have one restore point dated 4/2. however, since I rarely use the function (other than pulling specific build information), so it is entirely possible I had the problem then as well. I did try that restore point however, and it failed. It specifically said it could be related to an antivirus program, and I should temporarily disable my AV program to try again. Have not tried that yet because if there is a more critical failure during the process, I could be screwed. Saving that for the nuclear option. Also, I really want to know what the issue is. I figure that the process of pulling up the info that way is not something more users would do that often, this could be a systemic problem created by a recent update, and the average user has not seen this yet.

I also just noticed that if I click on the Control Panel, and select System from the menu, the same thing happens

Have You run a Admin CMD of sfc /scannow SFC /SCANNOW Command - System File Checker

americancritic said:

I would try safe mode to see if it does the same thing or not.

Yes, it does it in safe mode as well

Bat 1 said:

Have You run a Admin CMD of sfc /scannow SFC /SCANNOW Command - System File Checker

Yes, received the message:
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log C:\Windows\Logs\CBS\CBS.log.

when I view the CBS.log, it is well beyond my knowledge, but at the end it says this:

POQ 141 ends.
2017-04-16 23:46:54, Info CSI 000004df [SR] Repair complete
2017-04-16 23:46:54, Info CSI 000004e0 [SR] Committing transaction
2017-04-16 23:46:54, Info CSI 000004e1 Creating NT transaction (seq 2), objectname [6]"(null)"
2017-04-16 23:46:54, Info CSI 000004e2 Created NT transaction (seq 2) result 0x00000000, handle @0x1ea8
2017-04-16 23:46:55, Info CSI 000004e3@2017/4/17:03:46:55.767 CSI perf trace:
CSIPERF:TXCOMMIT;253861
2017-04-16 23:46:55, Info CSI 000004e4 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

Not sure what to do at this point

I searched the entire file for the word fail, and found these references.
2017-04-16 23:33:51, Info CBS Starting the TrustedInstaller main loop.
2017-04-16 23:33:51, Info CBS TrustedInstaller service starts successfully.
2017-04-16 23:33:51, Info CBS SQM: Initializing online with Windows opt-in: False
2017-04-16 23:33:51, Info CBS SQM: Cleaning up report files older than 10 days.
2017-04-16 23:33:51, Info CBS SQM: Requesting upload of all unsent reports.
2017-04-16 23:33:51, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2017-04-16 23:33:51, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2017-04-16 23:33:51, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2017-04-16 23:33:51, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2017-04-16 23:33:51, Info CBS No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.

assuming you rebooted after the sfc scannow procedure above and the problem is still there, here are three more guesses at a fix..

start > programs > accessories > windows explorer > right click > properties > previous versions > select a previous version

control panel > programs > microsoft.net > uninstall/change > repair

explorer > organize > Folder Options > View > Advanced > Launch Folder Windows in a separate process