here's the comment area for today's blog post found at
http://zabkat.com/blog/disable-zipfolder-exploring.htm
blog: simple hack to disable zipfolders
Moderators: fgagnon, nikos, Site Mods
it just occured to me that the reason why MS disabled the unregistering of the zipfolder DLL and all the protection of the registry keys must be to make sure that ZIP files remain folders so that the system indexer can search in them. It makes sense!
so the recommendation is still not to disable zipfolders
so the recommendation is still not to disable zipfolders
Unless you disable both despicable things at the same time, as all reasonable people would.
(Except I did it the hard way a couple of years ago without any negative side effects.)
And if you keep looking for reasons why MS continually removes functionality from their toys, you're going to have a very irrational future.
(Except I did it the hard way a couple of years ago without any negative side effects.)
And if you keep looking for reasons why MS continually removes functionality from their toys, you're going to have a very irrational future.
Well, I wasn't referring to simple DLL unregistering... I was more thinking of this sort of thing...
There are those who consider at least some of that list as being functional. Not everyone, admittedly, but a few might bemoan the loss of hard links. And that's just on the filesystem level.What semantics or features of NTFS are no longer supported on ReFS? wrote:The NTFS features we have chosen to not support in ReFS are: named streams, object IDs, short names, compression, file level encryption (EFS), user data transactions, sparse, hard-links, extended attributes, and quotas.
Re: blog: simple hack to disable zipfolders
The only way I could get them to disappear from Windows Explorer was to also rename this key: HKEY_CLASSES_ROOT\CompressedFolder\CLSID.bak