@AlanD "...
Have a look in the Event Log to see if there
are any more diagnostics. Winkey +R "eventvwr". It
should be in the Application logs ..."
It strikes me that without prior experience, we don't even
know what to look for in any of the suggested
maintenance ( and troubleshooting ?) routines.
For example, in my Even Viewer, Application and Service
Logs, I see thousands of lines like these below, I'll start off
with Microsoft, Windows, API-Tracing, Operational:
The API Tracing engine discovered a mismatch for a
required manifest file. Information about the
mismatch is below.
Executable path: C:\Windows\System32\regsvr32.exe
Binary name: KERNEL32.dll
System manifest ID: {00611880-0000-0000-6000-000000000000}
Binary manifest ID: {0011e120-0000-0000-8018-610000000000}
- System
- Provider
[ Name] Microsoft-Windows-API-Tracing
[ Guid] {B98F0DB6-26E2-4A66-89FC-32A9A6A9AF61}
EventID 1
Version 0
Level 4
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2021-07-21T04:47:27.437120800Z
EventRecordID 20
Correlation
- Execution
[ ProcessID] 9020
[ ThreadID] 11128
Channel Microsoft-Windows-API-Tracing/Operational
Computer D2400X2-W3503
- Security
[ UserID] S-1-5-21-1062448468-2640603965-20612060-1001
- UserData
- ManifestMismatchEvent
ExecutablePath C:\Windows\System32\regsvr32.exe
BinaryName KERNEL32.dll
SystemManifestId {00611880-0000-0000-6000-000000000000}
BinaryManifestId {0011E120-0000-0000-8018-610000000000}
Binary data:
In Words
0000: 32ELRNKE ll.d
In Bytes
0000: KE RN EL 32 .d ll
What would I do with that information?
And what would I be looking for in the first place?
In other words, is that information even relevant to my
own situation?
- - - - -
Interesting spread of random troubleshooting hints,
though.
- - - - -
Still awaiting any follow-up from @AvaDuncan.
But that's not slowing us down, eh?