How do I get rid of the document-type clutter in the Windows Right-Click New menu?

How do we remove useless clutter in the Windows "Right-Click New" command?
http://www.bild.me/bild.php?file=1364896Clipboard01.jpg

Windows Update bricked my old hard drive so I'm forced to set up Microsoft
Windows again, starting from scratch, on a new blank hard drive.

All I ever want is:
a. New Folder
b. New Shortcut
c. New Text Document

That's it. Nothing more than that. Forever.
How do I get rid of the other clutter in the Windows Right-Click New menu?

"ultred ragnusen" wrote

| How do we remove useless clutter in the Windows "Right-Click New" command?

Wasn't this recently discussed? On XP it involves
ShellNew subkeys under HKCR. For whatever menu
items you see, there will be a corresponding ShellNew
key under that file extension. Delete that key and the
menu item disappears. Unfortunately, some
programs will add those things without asking (Libre
Office is a nasty one) and others will even replace the
key if you delete it.

I assume 7 and 10 work the same way, but I've
never actually checked either.
On XP you can also do it more eassily with TweakUI
XP but I think that was the last version of TweakUI.

On 2018-02-13 20:55, ultred ragnusen wrote:

How do we remove useless clutter in the Windows "Right-Click New" command?
http://www.bild.me/bild.php?file=1364896Clipboard01.jpg

Windows Update bricked my old hard drive so I'm forced to set up Microsoft
Windows again, starting from scratch, on a new blank hard drive.

All I ever want is:
a. New Folder
b. New Shortcut
c. New Text Document

That's it. Nothing more than that. Forever.
How do I get rid of the other clutter in the Windows Right-Click New menu?

https://www.nirsoft.net/utils/shell_menu_new.html

Be aware that if you have MS Office, it will Re-Enable it's Shell-New
**** every now and again as updates come in. For that you need to run a
script in Task Scheduler, say once a day. The script will look like this
(for Excel 2016):

REG DELETE "HKCR\.xlsx\Excel.Sheet.12\ShellNew" /f

Regards,

--
! _\|/_ Sylvain /
! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society
oO-( )-Oo Money is the root of all evil, and man needs roots.

wrote:

And if you're talking about right clicking a black place and doing "NEW"
for a new folder etc. then this will allow you to de-clutter this.
http://www.nirsoft.net/utils/shell_menu_new.html

Thank you for that advice which instantly removed unwanted right click
"new" clutter.

http://www.bild.me/bild.php?file=393...ellmenunew.jpg

wrote:

https://www.nirsoft.net/utils/shell_menu_new.html

Thanks for offering that advice.

The Nirsoft Shell Menu New worked instantly, like a charm.

http://www.bild.me/bild.php?file=604...l_new_menu.jpg

On 2/13/2018 8:55 PM, ultred ragnusen wrote:
How do we remove useless clutter in the Windows "Right-Click New" command?
http://www.bild.me/bild.php?file=1364896Clipboard01.jpg

Windows Update bricked my old hard drive so I'm forced to set up Microsoft
Windows again, starting from scratch, on a new blank hard drive.

All I ever want is:
a. New Folder
b. New Shortcut
c. New Text Document

That's it. Nothing more than that. Forever.
How do I get rid of the other clutter in the Windows Right-Click New menu?

You can look at these two items to edit right-clicking file/folder items.
http://www.nirsoft.net/utils/shell_menu_view.html
and
http://www.nirsoft.net/utils/shexview.html

And if you're talking about right clicking a black place and doing "NEW"
for a new folder etc. then this will allow you to de-clutter this.
http://www.nirsoft.net/utils/shell_menu_new.html

On Tue, 13 Feb 2018 17:55:24 -0800, ultred ragnusen
wrote:

How do we remove useless clutter in the Windows "Right-Click New" command?
http://www.bild.me/bild.php?file=1364896Clipboard01.jpg

Windows Update bricked my old hard drive so I'm forced to set up Microsoft
Windows again, starting from scratch, on a new blank hard drive.

All I ever want is:
a. New Folder
b. New Shortcut
c. New Text Document

That's it. Nothing more than that. Forever.
How do I get rid of the other clutter in the Windows Right-Click New menu?

Ever consider not using hard disks at all? I ropped my external HD
last week (was very sick and dropped it after using it in class with
students) and lost about 300 GB of movies I ripped from DVD. Had the
external device used an SSD, I wouldn't have lost a thing but HDs are
very fragile in comparison and don't have the reliability people today
expect.

wrote:

Ever consider not using hard disks at all? I ropped my external HD
last week (was very sick and dropped it after using it in class with
students) and lost about 300 GB of movies I ripped from DVD. Had the
external device used an SSD, I wouldn't have lost a thing but HDs are
very fragile in comparison and don't have the reliability people today
expect.

Funny you mention that, since I was debating whether to just buy a small
SSD for the operating system, and then float a bunch of USB drives around
for all other purposes.

wrote:

Ever consider not using hard disks at all?

Funny you mention that, since I was debating whether to just buy a small
SSD for the operating system, and then float a bunch of USB drives around
for all other purposes.

At the moment, even with an external SATA drive, I can't access my data.

Hence, I've lost so much data due to Microsoft updates bricking my system
that I would like to ask the related question of partitions.

Had I partitioned my hard drive into a C: and D: partition, with /just/ the
operating system on the C: partition, would that partitioning have
protected me from the Microsoft Update bricking my system such that I can
no longer access my data?

In answering that question, it's important to realize I only care about my
data. Specifically, I don't care about installed programs or the installed
operating system because both are easily re-installed.

It's only the data I care about, all of which is in the C:\data hierarchy.

If I had partitioned the hard drive such that the data was not on the C:
partition, would a subsequent and seemingly inevitable Microsoft bricking
of the operating system have saved the data?

ultred ragnusen wrote:
wrote:

Ever consider not using hard disks at all?
Funny you mention that, since I was debating whether to just buy a small
SSD for the operating system, and then float a bunch of USB drives around
for all other purposes.

At the moment, even with an external SATA drive, I can't access my data.

Hence, I've lost so much data due to Microsoft updates bricking my system
that I would like to ask the related question of partitions.

Had I partitioned my hard drive into a C: and D: partition, with /just/ the
operating system on the C: partition, would that partitioning have
protected me from the Microsoft Update bricking my system such that I can
no longer access my data?

In answering that question, it's important to realize I only care about my
data. Specifically, I don't care about installed programs or the installed
operating system because both are easily re-installed.

It's only the data I care about, all of which is in the C:\data hierarchy.

If I had partitioned the hard drive such that the data was not on the C:
partition, would a subsequent and seemingly inevitable Microsoft bricking
of the operating system have saved the data?

Have you tried TestDisk yet ?

When you "Quit" from the scanning it does, it has
an option to view files on a partition. AFAIK, you can
select files/folders while in the file view, and copy them
to another partition.

TestDisk is typically available on a Linux LiveDVD, without
even using the Package Manager on the DVD.

There is also a Windows version, but I can't tell right
now, how much of your computer room still works.

https://www.cgsecurity.org/wiki/TestDisk

The tool doesn't follow conventions all that well, but
with some luck you might see a dialog like this. I think
you can copy materials seen here, to another disk. From this
menu, I can't tell what "level" I'm at, or what menu selections
get me here.

https://forum.cgsecurity.org/phpBB3/...le.php?id=3853

In general, I do not recommend using the tool for one of
its primary purposes, which is re-computing the partition table.
Only the operator (human) knows how many partitions are really
present, and the scanning that tool does, it can find partitions
you deleted three years ago, and the partition header sector
never got overwritten. It's pretty hard for the tool to
compute a proper partition table, when it keeps hoovering up
artifacts you've completely forgotten about. Only with the
most careful hygiene and erasure of old stuff, can you make
a disk "TestDisk" ready for some future disaster. There is
no substitute in this matter, for human reasoning and knowledge
of what the disk *should* look like. Don't just click "write
new partition table?" without checking and rechecking the
table it proposes to write. I even found a case where
partition 3 and partition 4 overlapped - if I had accepted
the partition table, and written it, at least one of those
partitions would be ruined on the next reboot.

Paul

In message , ultred ragnusen
writes:
[]
Had I partitioned my hard drive into a C: and D: partition, with /just/ the
operating system on the C: partition, would that partitioning have
protected me from the Microsoft Update bricking my system such that I can
no longer access my data?

Provided your OS doesn't use some _very_ odd control of the file system,
you should be able to access a d: partition by connecting the drive to
some other system. Or, assuming you can reinstall the (or any other) OS
on C: without upsetting the arrangement of partitions, you should be
able to access it on this computer.

In answering that question, it's important to realize I only care about my
data. Specifically, I don't care about installed programs or the installed
operating system because both are easily re-installed.

That's what I do - not just the OS, but installed software, on C:, data
on D:. I regularly (though not often enough of course) image C:, using
Macrium; I just copy (though SyncToy makes that faster) D:.

It's only the data I care about, all of which is in the C:\data hierarchy.

I generally try to keep my data away from the OS - even when I was on XP

If I had partitioned the hard drive such that the data was not on the C:
partition, would a subsequent and seemingly inevitable Microsoft bricking
of the operating system have saved the data?

Well, made it more possible to get at it if you had to reinstall, even
if that meant scrapping C:, as long as it didn't screw the partition
table.

I guess C:\data (though it would appear as something like F:\data) would
still have been accessible if you'd taken the disc out and connected it
to another computer. But IMO, and that of many, keeping data off C: is a
good policy. Not _everyone_ agrees, though.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Bother,"saidPoohwhenhisspacebarrefusedtowork.

wrote:

Provided your OS doesn't use some _very_ odd control of the file system,
you should be able to access a d: partition by connecting the drive to
some other system.

Alas, your wisdom comes too late for me ... this time.
But from now on, since Microsoft is killing me with these failed mandatory
updates, I am forced to go back in time, oh, what? Twenty years? And keep
the operating system on partition C and the data on partition D. Sigh.


I'll look up how big a C: partition is for just Windows, were my current
"Windows" directory is 14.7GB.

I assume "partition magic" is still the winner for partitioning after the
fact?

Or, assuming you can reinstall the (or any other) OS
on C: without upsetting the arrangement of partitions, you should be
able to access it on this computer.

Right now, with the failed windows update on the old (now removed) hard
drive, had the data been on a different partition than that damn operating
system, that would have been the way to save my data.

Lesson learned. I thought these days were gone where we had to protect
ourselves from the Windows OS eating itself up periodically, but, at least
for me, those days have returned. Sigh.

That's what I do - not just the OS, but installed software, on C:, data
on D:. I regularly (though not often enough of course) image C:, using
Macrium; I just copy (though SyncToy makes that faster) D:.

I realize most people make "images" but my philosophy is far simpler in
that I don't care about the installed programs - nor do I care about the
operating system - they can always be re-installed.

All I care about is my data which I keep, separately, by design, in
C:\data, but which, in the future, will, of necessity, regrettably, be on a
different partition.

There is no other way to save myself from Microsoft chewing up the
operating system again, and again, and again. And again. It's frustrating,
so pardon my frustration.


It's only the data I care about, all of which is in the C:\data hierarchy.

I generally try to keep my data away from the OS - even when I was on XP.

From Win95 to Win2K to WinXP and beyond, I have long learned not to trust
the Microsoft operating system. Windows 7 had gained my trust, but, as I
found out recently, it was a false trust, so, I'm back to not trusting the
OS to not eat itself periodically. Sigh. I can't enumerate my pent-up
frustration with Microsoft - I can't say worse things about them than I am
thinking right now.

Well, made it more possible to get at it if you had to reinstall, even
if that meant scrapping C:, as long as it didn't screw the partition
table.

Yes. I have "re" learned the lesson that you have to protect your data from
Microsoft. It's an old lesson, which I had thought was from a bygone era -
but it has reared its ugly head yet again ... Damn you Microsoft.

Fooled me once (long ago), and then gained my trust with Windows 7.
And now fooled me twice with Windows 10.

I guess C:\data (though it would appear as something like F:\data) would
still have been accessible if you'd taken the disc out and connected it
to another computer. But IMO, and that of many, keeping data off C: is a
good policy. Not _everyone_ agrees, though.

Even though I don't like the inconvenience, my data, henceforth, will be
going on a separate partition from the operating system.

I assume partition magic is the way to go to create that partition after
the fact - if not - then I'll just back up my new data (there isn't much
anyway since all the good data is on the hdd that Microsoft Update ****ed
up) and re-install the OS.

Looking for how big to make that C: os partition, I note my current Windows
directory takes up 14.7GB with 107K files, so, probably double that would
make a good partition size for C:, don't you think?

ultred ragnusen wrote:
wrote:

Provided your OS doesn't use some _very_ odd control of the file system,
you should be able to access a d: partition by connecting the drive to
some other system.

Alas, your wisdom comes too late for me ... this time.
But from now on, since Microsoft is killing me with these failed mandatory
updates, I am forced to go back in time, oh, what? Twenty years? And keep
the operating system on partition C and the data on partition D. Sigh.

I just rescued my Insider install tonight. At first
I thought I would have to reinstall, but a combination of
two calls to CHKDSK fixed it. I took my Win10 disk to
my Win8.1 setup, and ran CHKDSK from there.

chkdsk /offlinescanandfix M: === claims to "queue something for repair"
chkdsk /F M: === normal fix
chkdsk M: === verify it is really clean
(because I've been lied to before...)

I tried a couple /F, one after another, and that didn't work.
I tried the /offlinescanandfix by itself, and it wasn't enough.
But applying both commands, seemed to make a difference. I
had never heard of "/offlinescanandfix" until tonight.

*******

Moving a User Account to D: is "Not Recommended".

While Microsoft provides Junction Points to redirect certain
parts of a setup to other partitions, these fall flat on their
face when the OS is upgraded. And since Windows 10 is the
"Queen of Upgrades", constantly upgrading itself, you would
be driven crazy by a constant need to moving the account back
to C: while the upgrade runs.

So I wouldn't try that.

You can install using an old version of Win10, move the user
account to D: , then use a second DVD with a newer version of
Win10, and see whether they've fixed the installer to handle
that properly or not.

Paul

Two points. Make a good estimate as to how much the OS is going to take,
then double or triple it to allow for the always present size creep. It is
a lot easier to set aside the space now than to try and enlarge a partition
later, especially when it is the first partition on the drive.

I am currently on Windows 10. Microsoft created a directory tree for me
under \users, which I don't use at all. I use a directory on my data drive
for all my user functions. I have been doing this back to when the user
account was created under \Documents and settings, and have had no
problems.

As far as handling the original question, this article gives some useful
advice and directions: https://www.howtogeek.com/howto/windows-vista/how-
to-clean-up-your-messy-windows-context-menu/

In message , Tim
writes:
Two points. Make a good estimate as to how much the OS is going to take,
then double or triple it to allow for the always present size creep. It is

Seconded, though see other post.

a lot easier to set aside the space now than to try and enlarge a partition
later, especially when it is the first partition on the drive.

I am currently on Windows 10. Microsoft created a directory tree for me
under \users, which I don't use at all. I use a directory on my data drive

You think you don't, but you probably are doing, even if you don't want
to - your desktop and start menu are probably there, for example.

for all my user functions. I have been doing this back to when the user
account was created under \Documents and settings, and have had no
problems.
[]
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Paxman, the man who has never used one sneer when three would do
- Elizabeth Day, RT 2015/5/2-8