Serious flaw discovered in Windows Vista's Explorer


Recommended Posts

For anyone who is interested, here are the reproduction steps:

  1. Click on Start, and then click on Documents.
  2. In the Search entry box, type "NOT Shortcut" (without the quotes).
  3. Click on the "Save Search" button and save the search query as "Search Test".

I've removed the rest of the post due to the un-necessary amount of spam that I have received in the past 24 hours.

Edited by iCeFuSiOn

Very close to being blogspam. This is a serious flaw? Worst case scenario is the explorer process crashes and restarts without even restarting the OS. It may have taken down XP, but Vista just restarts the process and it's fine. Should MS fix it...of course. Is it a major flaw that's going to have any real impact, no. MS can fix it easily with a patch. Nice try to fabricate an issue out of nothing though. In fact demonstrates how Vista is much more robust against these sort of glitches than XP ever was.

Uhh... so you're searching for something that is NOT a shortcut? ie: pretty much everything? What do you expect to happen? :laugh:

If you're trying to search for documents only and the explorer brings back a list of shortcuts as well, NOT Shortcut will hide them. What it ISN'T supposed to do is crash the shell. This was bugged for SP1 and was marked as "won't fix".

If you're trying to search for documents only and the explorer brings back a list of shortcuts as well, NOT Shortcut will hide them. What it ISN'T supposed to do is crash the shell. This was bugged for SP1 and was marked as "won't fix".

Right, but usually you have something like "<some doc title> NOT Shortcut" and that doesn't crash, in fact it works exactly as expected. But placing just "NOT Shortcut" without any other filter does crash it instantly. So, yea, it crashes if that is your intention, but really this isn't much of an issue. Although it should probably be fixed, it's really not a big deal. Either way, I'm sure a patch will be released eventually. Probably after SP1, though.

I won't call this a serious but probably an unfortunate bug. Vista has other issues that are more important that this. Such as slow copying speeds and folder view thingy.

If you're trying to search for documents only and the explorer brings back a list of shortcuts as well, NOT Shortcut will hide them. What it ISN'T supposed to do is crash the shell. This was bugged for SP1 and was marked as "won't fix".

can use kind:document ? or just remove appdata folder from your index locations...that is what I do.

:rofl:

And to think I actually expected to read about a serious flaw...

Good grief, even in XP bringing back a crashed explorer is as easy as bringing up the task manager and doing a File >> Run explorer.exe

Apparently Vista does that all for you. Hardly anything to bash Vista for.

Not to mention that nobody out there even searches for "NOT Shortcut" by itself (given by the fact that it took over a year to even find this flaw...)

-Spenser

Why are we the source?

heh. we say they are the sourc they say it's us. A nice vicious cycle of sourcing.

Anyway it doesn't seem overly serious but it definitely should be fixed. I doubt it will kill anyone but it's blemishes like this that day in day out tarnish Vista's image. It's not the most pressing issue by all means, but still should be looked at.

We can only curse at things like this because WinFS would have certainly avoided such problems.

*sigh*

:ike:

Go look up WinFS and come back and give us a report on it. WinFS is not what you think it is. ;)

Why are we the source?

He changed it. Here's the original link: http://www.windows-now.com/blogs/kmkenney/...plorer-bug.aspx

As I said... This post is total flame bait and some people have already bitten the hook. ;)

wow the thread title and original post really tries to make this sound like a big deal. unfortunately for them it really isn't i'm sure it will be fixed but i wonder how many times people actually search for NOT shortcut. and anyway explorer restarts quickly really not much of a problem. if this is a seriuos flaw i would like to see how the author would describe all the problems that device drivers are causing in vista.

At a time where everyone is anxiously awaiting the upcoming service pack for Windows Vista (and while others flock back to Windows XP in droves), yet another flaw in the Windows Vista operating system has been discovered that can bring the Windows shell ("Windows Explorer") to its knees within 20 seconds. Even worse, this issue occurs under every day usage of the operating system if you use the Search function regularly with boolean search operators.

  1. Click on Start, and then click on Documents.
  2. In the Search entry box, type "NOT Shortcut" (without the quotes).
  3. Click on the "Save Search" button and save the search query as "Search Test".

This has been confirmed as a flaw in Windows Vista (all editions) and Windows Vista 64-bit (all editions), and even worse, the issue still occurs on the latest release candidate for Service Pack 1, and has been marked as "will not be fixed". The bigger question is, will Microsoft step up to the plate and fix this issue or will they let it pass on by while they work heavily on Windows "7", ignoring the fact that Windows Vista still has flaws and inconsistancies that are seeing larger companies hold back deployment until 2009 or even skip Vista?

Source of instructions to reproduce issue: ActiveWin.com

So from this we can learn a few things.

1) Vista must be in better shape and more on track and stable than the anti-Vista zealots would like for people to believe if it has taken a year for something like this to be classified as a serious flaw. For people that can think for themselves, this is the best pro-Vista post in history...

2) The person that found this flaw is a bit scary to expect this to be a valid search, especially so important to save it as a Search Folder. But hey, everyone to their own thing, so I'm over the scary part.

3) The person that posted this thinks MS is heavily working on Windows 7. Well it is true MS's NT cycle always starts at the end of a product release, so we can assume they are working on Windows 7. However, it is time for the idiots that keep running around thinking MinWin is Windows 7 or any different than the 'tight' kernel that is already in Vista and all previous versions of NT to wake up and watch the presentation or talk to someone at Microsoft for an accurate source on the subject. Windows 7 is not very active yet, and its kernel technology is the same as Vista, and it is scary that after 15 years of NT, people don't yet realize that the NT kernel is in fact very tight and small when you remove the API interface layers. (NT is a light API interface hybrid kernel technology) - This is why MinWin was a basic recompile of Vista kernel with the external APIs turned off, PERIOD.

4) Let's hope the person that found this fatal flaw doesn't do a nested search in a search that is recursive. They will really be mad at Windows then... Which points out another good thing about this bug, instead of dragging the system to a grind in an endless loop, or even choking, Vista just restarts Explorer and goes on its way. PS It will only restart the 'Folder Window' and not fully restart Explorer if you have "Launch folder windows in a separate process" (PS Which is handy to turn on)

Now for the unknown:

There is already an easy fix for this, pick a different freaking syntax, Vista has the most diverse search engine in OS history, with the most extensive set of search options including natural language and strict syntax as the user chooses.

Here is the 'fix' or way to perform the search effortlessly without killing Explorer if you really want to do this search:

NOT (ext:lnk OR ext:url)

-This also excludes Internet shortcuts, and is more accurate as you don't get folders in the mix of results.

NOT ext:lnk

-This is if you only want to exclude plain shortcuts and not Internet shortcuts, and again works better as it doesn't mix folders in the results.

You could also do:

-(ext:lnk OR ext:url)

or

-ext:lnk

Get the idea here? There are numerous ways to get the same results that don't involve killing Explorer

Now with that MAJOR flaw out of the way, this would be a good time to remind people that the search features in Vista are pretty powerful in doing more than just searching for items.

Look up a tool called Start++ from brandontools.com - (it is handy) and from it you can get an idea of how powerful the searching system is and how it can be extended in basic shell and commandline usage even. (Most people don't realize you can get search results in a CMD prompt, or from within their applications.)

Also for people doing more than causal searches, take a minute and read some up on some of the syntax options Vista offers and see why it makes Leopard and even Google Desktop Search look like toys.

This is a good reference page to begin with for the basics of advanced searching in Vista:

http://search.msn.com/docs/toolbar.aspx?t=...earchSyntax.htm

So from this we can learn a few things.

1) Vista must be in better shape and more on track and stable than the anti-Vista zealots would like for people to believe if it has taken a year for something like this to be classified as a serious flaw. For people that can think for themselves, this is the best pro-Vista post in history...

2) The person that found this flaw is a bit scary to expect this to be a valid search, especially so important to save it as a Search Folder. But hey, everyone to their own thing, so I'm over the scary part.

3) The person that posted this thinks MS is heavily working on Windows 7. Well it is true MS's NT cycle always starts at the end of a product release, so we can assume they are working on Windows 7. However, it is time for the idiots that keep running around thinking MinWin is Windows 7 or any different than the 'tight' kernel that is already in Vista and all previous versions of NT to wake up and watch the presentation or talk to someone at Microsoft for an accurate source on the subject. Windows 7 is not very active yet, and its kernel technology is the same as Vista, and it is scary that after 15 years of NT, people don't yet realize that the NT kernel is in fact very tight and small when you remove the API interface layers. (NT is a light API interface hybrid kernel technology) - This is why MinWin was a basic recompile of Vista kernel with the external APIs turned off, PERIOD.

4) Let's hope the person that found this fatal flaw doesn't do a nested search in a search that is recursive. They will really be mad at Windows then... Which points out another good thing about this bug, instead of dragging the system to a grind in an endless loop, or even choking, Vista just restarts Explorer and goes on its way. PS It will only restart the 'Folder Window' and not fully restart Explorer if you have "Launch folder windows in a separate process" (PS Which is handy to turn on)

Now for the unknown:

There is already an easy fix for this, pick a different freaking syntax, Vista has the most diverse search engine in OS history, with the most extensive set of search options including natural language and strict syntax as the user chooses.

Here is the 'fix' or way to perform the search effortlessly without killing Explorer if you really want to do this search:

NOT (ext:lnk OR ext:url)

-This also excludes Internet shortcuts, and is more accurate as you don't get folders in the mix of results.

NOT ext:lnk

-This is if you only want to exclude plain shortcuts and not Internet shortcuts, and again works better as it doesn't mix folders in the results.

You could also do:

-(ext:lnk OR ext:url)

or

-ext:lnk

Get the idea here? There are numerous ways to get the same results that don't involve killing Explorer

Now with that MAJOR flaw out of the way, this would be a good time to remind people that the search features in Vista are pretty powerful in doing more than just searching for items.

Look up a tool called Start++ from brandontools.com - (it is handy) and from it you can get an idea of how powerful the searching system is and how it can be extended in basic shell and commandline usage even. (Most people don't realize you can get search results in a CMD prompt, or from within their applications.)

Also for people doing more than causal searches, take a minute and read some up on some of the syntax options Vista offers and see why it makes Leopard and even Google Desktop Search look like toys.

This is a good reference page to begin with for the basics of advanced searching in Vista:

http://search.msn.com/docs/toolbar.aspx?t=...earchSyntax.htm

Actually, about the MinWin thing, the Core effort (which is the sliced off APIs) used to be called MinWin, but there's another effort to remake the kernel called MinWin and that does involve changing the kernel architecture.

The current slimmed-down kernel need the entire source tree to be built to build the kernel, because even though it doesn't call the APIs above, they're still needed to complete dependencies.

The new MinWin will enable the kernel to be built alone, or parts of the system, which helps in the layering, upkeep and testing of the OS.

Other than that, very informative post :)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • FxSound 1.2.9.0 / 1.2.10.0 Beta by Razvan Serea FxSound (formerly DFX Audio Enhancer / FxSound Enhancer) is now free, making high-quality audio enhancement accessible to everyone. Designed for all PC sound systems, from average setups to audiophile-grade equipment, it offers automatic or fully customizable processing. As automatic or customizable as you want, it utilizes the highest-grade processing to deliver more volume, better equalization, and a wider, deeper sound. For the serious audiophiles, FxSound gives you the tools to adjust the FxSound Effects and EQ to your exact preferences. Turn FxSound on and immediately hear the difference in sound quality. FxSound is ideal for budget audiophiles, music lovers, gamers, transcriptionists, Netflix enthusiasts, and more. It’s particularly beneficial for those relying on quiet laptop speakers or low-quality audio hardware. As a free tool, FxSound excels in boosting volume, enhancing bass, and improving sound quality. No other free EQ for Windows matches its ease of use. FxSound Is Now Completely Free and Unrestricted FxSound Pro is now free for everyone, not just those who can afford it. Get free and unrestricted access to better sound today. FxSound is now entirely supported by users. Click here to donate to help fund continued development and improvements to FxSound. FxSound 1.2.9.0 changelog: Auto save preset when Equalizer or Effects settings are changed Reset to factory defaults can reset the unsaved preset changes Settings dialog UI improvements for Audio and Equalizer sections Output device list is now displayed in the device preference order Preset is selected immediately when the preset for an active output device changes from settings Fixes and improvements in preferred output device selection Fixed crash issue #487 Fixed preset not getting applied and EQ flat after update (#403 and #472) Fixed system audio device not being restored on reboot (#483) Fixed preset export and import dialogs not shown when always on top is enabled Fixed audio not being restored on exit after the preset save dialog Fixed FxSound on/off handling on Windows session changes FxSound 1.2.10.0 Beta changelog: Command line options can now be applied to an already running instance of FxSound Command line option added to launch FxSound minimized to the system tray Fixed output device not being changed through hotkeys when FxSound is off (#524) Individual hotkeys can now be disabled with Delete key (#515) Fixed the but to prevent invalid hotkeys from being registered (#523) Bluetooth devices removed from device settings are removed from device preference list Fixed device detection failures Fixed application hang when retrieving the audio mix format fails Fixed presets import dialog file name combo box text alignment Fixed output device not being applied through command line Fixed a delay blocking application load when minimizing to the system tray Fixed EQ band sliders not refreshing when switching number of bands (#521) Fixed user-set mute being overridden by FxSound Fixed icon visibility in ARM64 version Finnish language support added Corrected Persian translations Download: FxSound 1.2.9.0 | ARM64 | ~70.0 MB (Open Source) Download: FxSound 1.2.10.0 Beta | ARM64 View: FxSound Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • mIRC 7.84 Final by Razvan Serea mIRC is a full featured Internet Relay Chat client for Windows that can be used to communicate, share, play or work with others on IRC networks around the world, either in multi-user group conferences or in one-to-one private discussions. It has a clean, practical interface that is highly configurable and supports features such as buddy lists, file transfers, multi-server connections, SSL encryption, proxy support, UTF-8 display, customizable sounds, spoken messages, tray notifications, message logging, and more. mIRC also has a powerful scripting language that can be used both to automate mIRC and to create applications that perform a wide range of functions from network communications to playing games. mIRC has been in development for over a decade and is constantly being improved and updated with new technologies. mIRC 7.84 changelog: Added custom dialog editbox option 'optional' for grayed out optional text. Fixed DirectShow temporary wave file not being deleted on exit. Changed $urlget() to retry a connection without compression in the event of an error. Updated code signing certificate to use Azure Artifact Signing. Fixed menubar display bug when in dark mode. Fixed /server -a not preserving existing entry's codepage. Fixed Address Book nick colors "idle time" display bug. Changed installer to no longer require administrator access on startup. Added support for displaying an MDI window's System menu when right-clicking its titlebar. Updated libararies to OpenSSL v3.5.7, TagLib v2.2.1, Zlib v1.3.2, and ADA v0.5.5. Updated CA root certificates cacert.pem file. For a full list of recent changes, please see the versions.txt file. Download: mIRC 7.84 | 4.3 MB (Shareware) View: mIRC Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You might be right... Look at his name, hiding in plain sight: hAmId.
    • ExplorerPatcher 26100.8457.70.3 by Razvan Serea ExplorerPatcher is a versatile and free tool that allows you to tweak and enhance the Windows Explorer. It comes with a range of useful features, including the ability to add new context menu items, change file name colors, and enable hidden features. Feature summary Choose between Windows 11 or Windows 10 taskbar (with labels support, small icons and lots of customization). Disable Windows 11 context menu and command bar in File Explorer and more. Open Start to All apps by default, choose number of frequent apps to show, display on active monitor and more. Choose between the Windows 11, Windows 10 and Windows NT Alt-Tab window switcher with customization. Lots of quality of life improvements for the shell, like: Skin tray menus to match Windows style, make them behave like flyouts and center them relative to the icon. Choose action when left and/or right clicking the network icon. Revert to the Windows 7 search box in File Explorer, or disable Windows Search altogether. Disable immersive menus and use mitigations that help you run the real classic theme without glitches. Discover the program's full range of features by reading this wiki article. ExplorerPatcher 26100.8457.70.3 changelog: Tested on OS builds 22621.4317, 22631.7079, 26100.6899, 26100.8037, 26200.8246, 26200.8457, 26300.8493, and 28000.2113. TIP: Windows Defender no longer flags ExplorerPatcher. It is no longer needed to configure Defender exclusions. Enjoy! Important Update for Windows Insider Users If you're running Windows 11 Beta build 26220.8474 or Experimental build 26300.8493, updating ExplorerPatcher is highly recommended. Microsoft has removed parts of the old Windows 10 Start menu from these builds, which caused ExplorerPatcher's Windows 10-style taskbar and Start menu to crash. This update fixes those issues and ensures Explorer starts correctly after future Windows updates. Because the required components are no longer included in Windows, the Windows 10 Start menu option has been disabled on these builds and future builds that lack the necessary files. A temporary workaround is to replace StartTileData.dll with a version from build 26xxx.8457, but this solution may stop working in future releases. The good news: development on the Windows 10 Start menu isn't over yet. More updates are planned. Highlights Fixed crashes affecting the Windows 10 battery flyout on Windows builds 25951 and newer. As part of that fix, network flyout buttons now behave like they did before Windows 11 version 24H2. Changes to the Primary taskbar location on screen setting now apply instantly without requiring a restart. ExplorerPatcher no longer modifies Windows 11 taskbar auto-hide settings when Explorer starts. The Open Start in All apps by default option is now hidden when the new Windows 11 Start menu is enabled. Fixed Windows 10 Start menu crashes on very early Windows 11 builds (21996–22000.51). Fixed a crash in Registry Editor when switching to thumbnail view during registry import/export operations. Improved compatibility with recent Windows builds, especially ARM64 and upcoming 26H1 releases. Improved overall ARM64 performance. Added Greek language translations. Thanks to @KonVetsos! ep_taskbar Improvements ep_taskbar now supports all 43 Windows 11 display languages. Fixed several issues in the system tray and other taskbar components. For mod developers: DLL naming has been simplified and made easier to understand. For mod developers: internal TrayUI changes provide better stability across Windows builds that use different taskbar implementations. Windows 10 Start Menu Improvements To help preserve compatibility, ExplorerPatcher now includes a newly recreated version of the tile layout engine that Microsoft removed in build 26xxx.8474. Current limitations: Tiles may occasionally overlap when pinned in certain ways. Restarting StartMenuExperienceHost.exe or Explorer usually corrects the layout. Further improvements are planned. Additional Fixes Added a blacklist that prevents ExplorerPatcher's shell extension from loading inside specific applications where it may cause problems. Updated Windows 10 Start menu animation support for newer ARM64 Insider builds. Fixed a rare taskbar initialization deadlock that could occur during startup. Start10 Updates Addressed a new compatibility issue caused by Microsoft's ongoing removal of tablet mode code in Windows 11 25H2 Experimental builds. Pinned tiles are no longer reset after repeated crashes. Various wording and interface text improvements throughout the application. Translation and UI Several interface strings have been cleaned up and clarified. Thanks to @sefinek for wording improvements. Please consult the README for more details. Download: ExplorerPatcher 26100.8457.70.3 | ARM64 | ~11.0 MB (Open Source) View: ExplorerPatcher Home Page | Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This author may be AI..... we just...... don't know.... lol AI is taking over.....run for the hills!
  • Recent Achievements

    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      +Edouard
      165
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Michael Scrip
      87
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!