Windows 7 system persists with Recent Items

This is a Windows 7 system just commissioned.  Classic Shell is installed.

  • Classic Shell has been configured to disable the recently used items area.
  • The group policy has been changed to disable this area.
  • The registry has been edited to reduce the number of items in the recently used list to zero.

Nonetheless, the system is still content to put each recently used program into that list, as shown in the screenshot below.

I have run out of hammers to hit this problem with.  Suggestions on how to remedy the issue will be gladly received.

W7 recent items on menu
LVL 33
Dr. KlahnPrincipal Software EngineerAsked:
Who is Participating?
 
☠ MASQ ☠Connect With a Mentor Commented:
In Taskbar and Start Menu options > Start Menu tab are you seeing the Privacy Options checked?

IIRC Classic Shell removes your jumplists of recently used each restart but allows them to build up in the meantime.

This is the stock registry location and setting
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
"NoRecentDocsHistory"=dword:00000001

Open in new window


Note this doesn't hide the placemarker for recent items so some users could navigate through their history, even if you have recent items disabled, and get to root of C: if that's not limited by GPO somewhere else.
0
 
Dr. KlahnPrincipal Software EngineerAuthor Commented:
The Privacy checkboxes are both unchecked and both are grayed out.

Regedit indicates that both NoRecentDocsHistory and NoRecentDocsMenu are set to 1.
0
 
Dr. KlahnPrincipal Software EngineerAuthor Commented:
Further inspection of Classic Shell indicated that

a) It was perfectly aware that those items should not be displayed, as they were greyed out and flagged with a red lock, and
b) Nevertheless, there was an option on a different tab that managed to override Group Policy and the Registry.
0
 
Dr. KlahnPrincipal Software EngineerAuthor Commented:
Points to Masq for pointing out where the problem was likely to be found in the other associated thread.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.