Jump to content

Recommended Posts

Posted (edited)

I have removed a lot of stuff from Server 2003, I am having problems

deleting a registry entry that relates to a blank folder in Control Panel.

The blank folders description says:

"Schedule computer tasks to run automatically."

I have removed Task Scheduler so I don't want this folder appearing here.

If I search my registry for "Schedule computer tasks to run automatically"

I can find the entry under this key:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\MUICache]

When I make a .REG file to delete it like this:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\MUICache]

"@C:\WINDOWS\system32\SHELL32.dll,-22923"=-

It does not delete the entry.

1 - Yes I am logged in as Administrator.

2 - This is unattended, so I have tried doing this tweak at the T-12 minute

stage from cmdlines.txt, both trying to remove the entry under "HKCU" and

also "HKU\.DEFAULT" - it won't work.

3 - If I manually delete the entry it comes back again.

4 - I do not have any programs running that might be "protecting" the registry.

5 - I used Dependency Walker to see if the file REG.EXE depends on any

other files, all the DLL files listed in Dependency Walker were put back in

system32 and all the ones I could register were registered, it still does not

remove the entry.

6 - I have tried referring to the entry as:

"@C:\WINDOWS\system32\SHELL32.dll,-22923"

AND

"@C:\\WINDOWS\\system32\\SHELL32.dll,-22923"

7 - I tried it with a batch file like this:

REG DELETE "HKCU\Software\Microsoft\Windows\ShellNoRoam\MUICache" /V "@C:\WINDOWS\system32\SHELL32.dll,-22923" /F

REG DELETE "HKU\.DEFAULT\Software\Microsoft\Windows\ShellNoRoam\MUICache" /V "@C:\\WINDOWS\\system32\\SHELL32.dll,-22923" /F

Doesn't work, batch files OR reg files, nothing is working!

---------------------------------------------------------------------------------------------------------------------------------

Would it be possible to edit an INF file in the Windows setup so this entry

is not created in the first place? Which INF file would it be? There are more

than 150 .IN_ files in I386 :(

---------------------------------------------------------------------------------------------------------------------------------

Edited by LeveL

Posted

I worked it out, I think. :blushing:

All the stuff in the first post doesn't apply, I removed this key

and it removes the folder...

Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]


;

Posted (edited)
Would it be possible to edit an INF file in the Windows setup so this entry

is not created in the first place? Which INF file would it be? There are more

than 150 .IN_ files in I386

Yes

If you REALLY want to remove it from installing in the first place, then copy all *.in_ files to a new directory and expand them all with expand -r *.in_ and then run a text search for the desired string, D6277990-4C6A-11CF-8D87-00AA0060F5BF

However. Sometimes DLLs create Reg keys, not INF files. (I know, I know).

So, instead of preventing, delete this at install by adding this line in INF format to an INF.

So, rewrite your line and add it to an INF file's DELREG section.

HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}"

Trouble is, edit an INF which is digitally protected and your install won't work.

So, ya gotta get the 2003 files to allow you to make the mods. Go to http://vorck.com/data/2003/ and grab the dll. setupapi, that is. ignore sakit, it doesnt apply and it would take me too long to describe what it does (you would have to be using it in conjunction with HFSLIP to strip junk out of 2003. go ahead and have a look in it if you like).

Edit: you can add your line to your own rewritten sakit.inf. you will find that in 2003 and xp there are a handfull of inf files that do nothing useful, and that's the place to add your tweaks. so, you could simply reuse my sakit and just rewrite it so it doesn't gut the registry so much and adapt it to your purposes.

note that doing this will make your 2003 incompatable with nlite, which relies on an unmodified setupapi file.

Edited by fdv
Posted

Thanks man, I don't need this info for doing this now but it is

certainly gonna be useful in future I am sure.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...