Well Brandonc, Hello again.
I am hopeful that you've had a great day.
My day was somewhat ordinary, which is to say, I had a hard time keeping up with it.
But I did use break and distraction times to sift through information that could help us here.
Lots of sifting, no nuggets.
It would just "seem like" there would be one or two main entries somewhere that would command this problem to be banished.
Yet it does not seem to be so.
There is a "slim" possibility that the Start - Run - (type)
regsvr32 /i shell32 - Enter could bump everything up a notch but expect success only if all other application values are sitting there waiting in their correct value settings.
<– Go ahead and give it a shot, once.
There is a sometimes offered series of about two dozen values to be registered that may affect a solution to a variety of problems, but no guarantee that it would help yours.
The kind of "scan" that we would hope would find and replace various missing or corrupt operating system files is the System File Checker (SFC /scannow) which
CatByte has already recommended much earlier and you indicated didn't help.
Question:
When you ran "sfc /scannow" …. How long did the scan take?
If it only took less than 2 minutes, then it didn't actually run and should be repeated until it runs completely (time varies between 7 minutes to half an hour)
If SFC does identify and replace any files, it should be run a second and even third or more times until it runs the full course without identifying any missing or corrupted files.
The other place where we may get some descriptive information is from Event viewer.
Start - Run - (type)
eventvwr.msc - Enter
Open the Event Viewer utility in your Administrative Tools control panel and look through your System and Application logs for entries flagged with "Error" or "Warning". Double-clicking on such an entry will open a properties window with more detailed information on the error; post the details from a representative sample of some of the different error messages. Don't post duplicates, but do tell us if a single even code is being repeated over and over.
In the Properties window of a given entry, click on the button with the graphic of two pieces of paper on it; the button is at the right of the window just below the up arrow/down arrow buttons. You won't see anything happen when you click the button, but it will copy all of the details to the Windows clipboard. You can then paste the details into your next post here.
Please run SFC /scannow from a command prompt
Start - (type)
cmd - Enter
At the blinking cursor - (type)
sfc /scannow <– notice the required space between "c" and "/"
let us know how the scan went…. meaning sit there and watch to see if it calls for and is replacing missing or corrupt files.
Sorry…. Almost as exciting as watching paint dry.
_______________
Next:
Have a look in Event Viewer — per the above instructions, and post back with any observations.
I'm going looking for someone smart enough to identify and fix this situation.
We've got some talented folks here. Something will turn up short of doing a Repair Installation (last resort)
Looking forward to hearing from you.
Doug
