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

    • TLDR. Here is a far better title (just a basic example): Windows 11 26H2 to allow disabling Web search results
    • Restore will get my vote, only if to see if things are any different, doubt it though but Labour and Conservatives too out of touch and same thing over and over and over…, Lib Dem who?
    • There is nothing wrong with this title. You have completely missed the plot when it comes to "clickbait." The issue was never that a title tries to entice you to click, that is how titles have worked for over 100 years. The issue is when the title subverts expectations, getting you to click expecting something that isn't there. The classic clickbait example is "Boyfriend caught cheating, what happens next will shock you," then what happened next is the girlfriend was upset...which is probably the least shocking outcome imaginable. If sounds like what you want is for the titles to be a collection of 10-word summaries that you can skim, get the just of the story, and only click if you want more details. That is not, never has been, and never will be what titles are. You can go all the way back to print newspapers during the great depression and see the same thing. The newspaper was locked in a vending machine, all you can see is the headline, you choose to put in 5¢ to buy the paper and read the rest if you want. Those headlines were written in a way to sell the paper, not just to provide a summery. Here are two actual headlines from that time, "Wall Street Lays an Egg," or "Stocks Hit Bottom?" Maybe you'd say something like "it was wrong then and it's still wrong now." Okay, fine opinion to have, but it isn't like Neowin is doing something unjurnalistic, they are just following the age-old standards for written media.
    • AMD 26.6.2 driver brings FSR 4.1 support to RDNA 3 RX 7000 series graphics cards by Pulasthi Ariyasinghe A new driver is rolling out to Radeon graphics hardware owners, and alongside support for new games, AMD has just made its FSR 4.1 upscaling tech available to an entire generation of its products. Last month, AMD announced it is answering community requests to bring FSR 4.1 to past generations of its Radeon graphics cards. This would be starting with RDNA 3 RX 7000 products. Right on schedule, this is what's rolling out now with the AMD Software: Adrenalin Edition 26.6.2 driver containing official support for over 300 games. Following this, AMD is planning to bring out RDNA 2 (RX 6000 series) support for FSR 4.1 sometime in early 2027. As for the games, this Adrenalin 26.6.2 driver is a recommended install for anyone jumping into Ubisoft's upcoming Assassin's Creed Black Flag Resynced remake or id Software's DOOM: The Dark Ages' Revelations expansion. The two fixed issues in this release are these: Intermittent application crash or driver timeout may be observed while playing RoadCraft on Radeon™ RX 7000 series products. Purple screen may be displayed when using an HP Reverb G2 headset with SteamVR on Radeon™ RX 6000 series graphics products. The known issues AMD is still working on are the following: Intermittent application crash or driver timeout may be observed while playing Battlefield 6 on AMD Ryzen AI 9 HX 370. AMD is actively working on a resolution with the developer to be released as soon as possible. Texture flickering or corruption may appear while playing Battlefield 6 with AMD Record and Stream on some AMD graphics products. AMD FSR Upscaling and AMD FSR Frame Generation may show as inactive in AMD Software: Adrenalin Edition while playing Battlefield 6 when enabled on Radeon™ RX 9000 series graphics products. Failure to install may be observed while installing AI Bundle components in some regions with limited access to HuggingFace and GitHub. Model flickering or rendering failure may be observed in Maxon Cinema 4D and Blender on Radeon RX 7000 series and above graphics products. Users experiencing this issue are recommended to install AMD Software: Adrenalin Edition 26.3.1. Intermittent application crash may be observed on some models while running Blender on Radeon RX 7000 and above graphics products. Users experiencing this issue are recommended to install AMD Software: Adrenalin Edition 26.3.1. The newly released AMD Software: Adrenalin Edition 26.6.2 driver is now available for download from the AMD Software app. Find the official changelog here.
  • Recent Achievements

    • Dedicated
      tuben earned a badge
      Dedicated
    • Week One Done
      mnsgroup earned a badge
      Week One Done
    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      525
    2. 2
      +Edouard
      199
    3. 3
      PsYcHoKiLLa
      94
    4. 4
      Michael Scrip
      82
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!