Author Topic: SuperFetch is not working. Unable to start access denied  (Read 4591 times)

0 Members and 1 Guest are viewing this topic.

Offline Cararta

  • Newbie
  • *
  • Join Date: Jun 2020
  • Posts: 1
  • Karma: 0
    • View Profile
SuperFetch is not working. Unable to start access denied
« on: June 11, 2020, 07:27:45 pm »
SysMain   SuperFetch
Dell optiplex gx620

Win 7 pro
using FireFox & Duck Duck

My computer is almost useless.  When try to open even notepad must wait

I searched on Microsoft people/community but can't figure out
how to repair.

Problems started after big storm, electric off & on..
when computer finally rebooted  (waited out the storm)   now my partition
on C: drive  which was labeled D:  is now gone. (that was used for backups of system(?)

biggest problem is when commenting on Facebook or Twitter
I cannot upload  images.  Also right now if I forget and type to
fast there will be a 'wait time' before text appears.

Also searching takes forever. 

FYI:  I am 80, still trying to live with Win 7...$$$$
From what I read at Microsoft  the problem has something to
do with Logo display?   
Can anyone help. 

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: SuperFetch is not working. Unable to start access denied
« Reply #1 on: June 12, 2020, 07:54:05 am »
The problem with storm damage is that it can be indeterminate.

Do you have any restore points that you could try ?

I don't know if this will help but you could try it if the restore points don't and that is to run a Command Prompt as a administrator.

You probably know how to do that, but go Start - type cmd then right click on cmd and select Run as administrator - accept the UAC then type sfc /scannow and press enter.

It can either report that it found no integrity violations, it had repaired all corruption or that it could repair some but not all corruption.

Type exit and press enter to close the command window.

Can you post a link to what you found about the logo cause - I don't know what to Google for.