Have a problem with cookies

[Abdou SoFT]

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

 

[writhziden]

Have you tried opening with an http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html 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.

 

[Brink]

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.

http://www.sevenforums.com/tutorials/94067-cookies-delete.html

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

and

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

Hope this helps,
Shawn

 

[writhziden]

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.

http://www.sevenforums.com/tutorials/94067-cookies-delete.html

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.

 

[Brink]

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.

 

[roncerr]

...You could also type shell:cookies and shell:Cookies\Low in the Run command dialog instead of the full paths below though.

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

and

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

​

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 Win7 admin type account.
​

 

[whs]

Hmm, very strange

 

[Brink]

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

 

[whs]

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.

 

[roncerr]

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.

 

[Brink]

Well, the registry entry for shell:Cookies and shell:Cookies\Low is below. You might check to see if your's has the same entries as below as a possible cause.

http://www.sevenforums.com/tutorials/4941-shell-command.html

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{2B0F765D-C0E9-4171-908E-08A611B84FF6}

Windows Registry Editor Version 5.00
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{2B0F765D-C0E9-4171-908E-08A611B84FF6}]
"Name"="Cookies"
"Category"=dword:00000004
"RelativePath"="Microsoft\\Windows\\Cookies"
"ParentFolder"="{3EB685DB-65F9-4CF6-A03A-E3EF65729F3D}"

also check:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{3EB685DB-65F9-4CF6-A03A-E3EF65729F3D}]
"Name"="AppData"
"Category"=dword:00000004
"RelativePath"="AppData\\Roaming"

 

[roncerr]

Both registry entries are exactly what I have; nevertheless, I ran the cookies.reg file you provided just to be sure. The problem remains, however as I pointed out above, none of the shell commands appear to work. (I tried several in the tutorial list, including shell:system.)

 

[Brink]

That is just strange Ron. If you create a new administrator account as a test, do they work while logged on to it?

 

[roncerr]

That is just strange Ron. If you create a new administrator account as a test, do they work while logged on to it?

No. Same behavior. The search box can't find "shell:system" and the run box error message says the same thing.

 

[Dwarf]

What about other shell:xxx commands?

 

[roncerr]

What about other shell:xxx commands?

See post #12 above.

 

[Brink]

Ron, I don't think I have ever seen where the shell commands did not work on a system before. Do you remember if they ever worked for you, and if so anything that you may have installed or changed a setting for that may have prevented them from working anymore?

 

[roncerr]

...Do you remember if they ever worked for you, and if so anything that you may have installed or changed a setting for that may have prevented them from working anymore?

I rarely use them (ok never) since I use Explorer. But when you mentioned shell:cookies it did seem like something I had seen working before, even on this computer. As I said, I have another almost "identical" install on another identical PC, however I install from a Windows disk, with separate customizations, program installations, and Windows Updates, so no two Windows installs can really be the same. So I suppose it's possible I did an extra customization on the one that doesn't work (the other does). Perhaps it requires a Windows Feature that I turned off, like indexing, for example.

 

[roncerr]

The mystery continues...I found one that works: "shell:windows". (I tried several from this list: System Folders in Windows 7.)

 

[Brink]

I don't know of a setting in Windows that would disable them. Possible 3rd party program the cause??