- Local time
- 6:02 PM
- Messages
- 70
You could always try reinstalling avast, then uninstall with Control Panel, uninstall a program, or Revo Uninstaller, then run Avastclean. It will most likely remove the rogue entries. Safe way if it will work! JoWazzoo is correct, it is not your issue, and altering the registry is usually not a good idea. If it ain't broke, don't fix it! Repair install will not alter those entries, at least is shouldn't!
I already ran AvastClean. Never mind, I'll leave those Avast entries where they are. As long as you are satisfied that the registry is OK, then let's move on please. Still don't know why Eusing "hangs" on "empty keys" but I can live with it.
So there are still 2 issues left to address:
1. I am going to swap in another keyboard temporarily. Maybe that's causing the F8 issue. Tried JoWazzoos link and yes, it boots directly into safe mode using msconfig. I don't get an advanced boot menu though, and can't get a choice "safe mode with networking" which is what I most often use.
2. I'd sure like to fix the missing/corrupt files that were originally found using SFC /scannow and don't know why I can't read that CBS logfile.
Last resort repair install if 1 and 2 can't be corrected. Will a repair install accomplish these two criteria?
My Computer
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- custom build
- OS
- Win 7 64 bit Home Premium
- CPU
- AMD A6 6400K
- Motherboard
- Gigabyte
- Memory
- 8 bg
- Hard Drives
- SSD plus HDD