Windows 7: Have a problem with cookies

HI

Dear brothers

When I want access to this track

Cookies

From the Run command

Tell me

Inaccessible to c:\users\ras\Cookies

Access is denied

Have you tried opening with an Elevated Command Prompt to increase your permissions?

To open Run with command prompt, type into the command prompt:

cd %systemroot%\System32

rundll32.exe shell32.dll,#61

Then you can run with administrative privileges.

Hello Abdou, and welcome to Seven Forums.

C:\Users\ras\Cookies is a junction point for backwards compatibility, and not a actual folder or shortcut. You will not be able to open this location no matter what method you try.


The location for your cookies is actually at the two hidden protected operating system folder locations below. You could also type shell:cookies and shell:Cookies\Low in the Run command dialog instead of the full paths below though.

Cookies - Delete

C:\Users\(User-Name)\AppData\Roaming\Microsoft\Windows\Cookies

and

C:\Users\(User-Name)\AppData\Roaming\Microsoft\Windows\Cookies\Low

Hope this helps,
Shawn

Thanks Shawn, I was not aware that running cookies, even elevated, would not open the correct directories. Appreciate the help.

Hello Mike,

You can open their locations in command prompt if you like, it's just that you cannot open junction points since they are not actually a real location. That's all.

The path is correct, but "shell:cookies" and "shell:cookies/low" don't work for me in the search box or the run box. Using Windows 7 admin type account.

Hmm, very strange

Strange indeed. They should both work for you in the Run command dialog and Start Menu search box.

Roncerr, I suggest you try another shell - e.g. shell:system - that should bring up the system32 folder. That is just to see whether the shell commands work.

Great suggestion! I did that and found that it finds many results with the word "shell" but nothing for "shell:system" or "shell:cookies". I also have another Windows 7 computer, installed and updated the same via Windows Update, for which those searches work correctly. So on the "no shell" computer I did some maintenance (disk cleanup, disk check w/reboot, sfc /scannow). I was surprised that sfc finished in only 10 minutes, found nothing to repair, and reported no integrity problems.

So how does one fix the shell feature? I tried Googling it but apparently no one else has had that problem.