PDA

View Full Version : Removing/adding stuff to the rightclick -> "new" folder


R.Wieser
May 1st 17, 08:51 PM
Hello all,

Some time ago I noticed a number of entries in my rightclick -> "new" folder
that I will probably never use. So, I set out to remove them. Which
seems to be harder as it should be. At least, the way I found to do it is
to go into regedit and rename the involved "ShellNew" keys. Which works
well, no problems there.

But now the question: I see many of such "ShellNew" keys, but only a few
appear in the "new" folder (example: excel.xls doesn't). Does anyone know
what makes, or doesn't make, a ShellNew key appear in the "new" folder ?

Regards,
Rudy Wieser

Paul[_32_]
May 1st 17, 11:58 PM
R.Wieser wrote:
> Hello all,
>
> Some time ago I noticed a number of entries in my rightclick -> "new" folder
> that I will probably never use. So, I set out to remove them. Which
> seems to be harder as it should be. At least, the way I found to do it is
> to go into regedit and rename the involved "ShellNew" keys. Which works
> well, no problems there.
>
> But now the question: I see many of such "ShellNew" keys, but only a few
> appear in the "new" folder (example: excel.xls doesn't). Does anyone know
> what makes, or doesn't make, a ShellNew key appear in the "new" folder ?
>
> Regards,
> Rudy Wieser
>
>

This one looks suspicious and might play a part.
Stuff isn't in the same order.

HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer\Discardable\PostSetup\ShellNew

https://s29.postimg.org/fq9qih36f/shellnew.gif

Paul

R.Wieser
May 2nd 17, 07:08 AM
Paul,

> This one looks suspicious and might play a part.

Thanks for that find.

Alas, a bit of testing (re-enabeling a suppressed ShellNew entry) showed
that that it gets updated with the re-enabled entry. In other words, it
seems to be a kind of cache.

Regards,
Rudy Wieser


-- Origional message:
Paul > schreef in berichtnieuws
...
> R.Wieser wrote:
> > Hello all,
> >
> > Some time ago I noticed a number of entries in my rightclick -> "new"
folder
> > that I will probably never use. So, I set out to remove them. Which
> > seems to be harder as it should be. At least, the way I found to do it
is
> > to go into regedit and rename the involved "ShellNew" keys. Which works
> > well, no problems there.
> >
> > But now the question: I see many of such "ShellNew" keys, but only a few
> > appear in the "new" folder (example: excel.xls doesn't). Does anyone
know
> > what makes, or doesn't make, a ShellNew key appear in the "new" folder ?
> >
> > Regards,
> > Rudy Wieser
> >
> >
>
> This one looks suspicious and might play a part.
> Stuff isn't in the same order.
>
>
HKCU\Software\Microsoft\Windows\CurrentVersion\Exp lorer\Discardable\PostSetu
p\ShellNew
>
> https://s29.postimg.org/fq9qih36f/shellnew.gif
>
> Paul

JJ[_11_]
May 2nd 17, 07:38 PM
On Tue, 2 May 2017 08:08:49 +0200, R.Wieser wrote:
>
> Alas, a bit of testing (re-enabeling a suppressed ShellNew entry) showed
> that that it gets updated with the re-enabled entry. In other words, it
> seems to be a kind of cache.

Some applications (e.g. MS-Office including some others) re-add the ShellNew
registry keys when the application or its ActiveX/COM is used.

R.Wieser
May 2nd 17, 09:18 PM
JJ,

> Some applications re-add the ShellNew registry keys when the
> application or its ActiveX/COM is used.

I've not yet noticed such a thing, but as I left the disabled ShellNew keys
in place (just prepended with an exclamantion mark) those will be(come) easy
to spot.

But thanks for the warning.

Regards,
Rudy Wieser


-- Origional message:
JJ > schreef in berichtnieuws
...
> On Tue, 2 May 2017 08:08:49 +0200, R.Wieser wrote:
> >
> > Alas, a bit of testing (re-enabeling a suppressed ShellNew entry) showed
> > that that it gets updated with the re-enabled entry. In other words, it
> > seems to be a kind of cache.
>
> Some applications (e.g. MS-Office including some others) re-add the
ShellNew
> registry keys when the application or its ActiveX/COM is used.

JJ[_11_]
May 3rd 17, 01:24 PM
On Tue, 2 May 2017 22:18:33 +0200, R.Wieser wrote:
>
> I've not yet noticed such a thing, but as I left the disabled ShellNew keys
> in place (just prepended with an exclamantion mark) those will be(come) easy
> to spot.

I locked some of the annoying sticky ShellNew by changing its registry key
permission so that no access to it is allowed. Or to keep it from being
changed by other application.

Google