Serious flaw discovered in Windows Vista's Explorer


Recommended Posts

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

Holy cow, think of the countless people who will be put into shambles, i mean, people search for NOT Shortcut all the time, and i for one always save my queries as search test.

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

*sigh*

:ike:

Acdtually, all three major components of WinFS IS in Vista, in the forms of Instant Search, VSC and som other stuff.

It doesn't crash my system :s

Windows Vista Home Premium with the RC of SP1.

It crashed my system without SP1, but didn't crash with SP1 so this is fixed with SP1 I guess. Either way, why is anyone searching for NOT shortcut in the first place? I mean most people search for specific files, not everything on their damn system. This is a non-issue IMO.

I love how people quickly defend Microsoft's Vista OS when people find issues with it. The right thing to do is expect this bug to be fixed. There is no excuse for not fixing a bug. You pay good money for it and in exchange you expect support for it, especially a the price tags of Vista's many flavours, why would you defend its flaws?

I'm not saying XP or anything else is perfect, but for christ sake people this is a PIECE OF SOFTWRE, not a cult or religion. Yes the person who posted about this bug probably hates Vista but it's a bug nevertheless regardless if the person is a Vista hater or supporter and a bug should eventually be fixed. It's as simple as that.

I love how people quickly defend Microsoft's Vista OS when people find issues with it. The right thing to do is expect this bug to be fixed. There is no excuse for not fixing a bug. You pay good money for it and in exchange you expect support for it, especially a the price tags of Vista's many flavours, why would you defend its flaws?

I'm not saying XP or anything else is perfect, but for christ sake people this is a PIECE OF SOFTWRE, not a cult or religion. Yes the person who posted about this bug probably hates Vista but it's a bug nevertheless regardless if the person is a Vista hater or supporter and a bug should eventually be fixed. It's as simple as that.

Yes, the bug should be fixed, but I don't care if they get around to fixing it in Vista SP1 or SP5 - I'll never encounter it, period. I'm more concerned about memory leaks and actual bugs that hamper my experience then some obscure bug I'll never accidentally encounter.

Please let us know when it proves to be a remotely exploitable buffer overflow that is usable as a program loader. Then we can upgrade its status to either serious or critical. At this point it's just a minor irritation, something that is in every version of every OS I've ever worked with. Pttht!

Interesting fallout from this...

Going back to 14 months ago...

I'm at the Microsoft Windows Vista October Beta Tour and am in one of three groups of ~40 of the Vists Beta Testers invited to spend 2 days at Microsoft, and Robert McLaws ( owner & admin of www.windows-now.com ) happens to be in my group - a very easy-to-talk-to guy who also knows what he talks about. I got to meet alot of very interesting people and renewed some very old (around 20-years-ago) friendships with former co-workers from various former employers.

...fast-forward to present time...

I see that the original post that generated this thread and the one on ActiveWin came from Robert's site - which causes me to raise my eyebrows slightly. I click on the link for the originating blog entry....and get ZIP from the website. I go back and see the list of Bloggers on the site, locate the author's blogs...and am greeted with this page. I go back and try to click on the actual blog entry - which now takes us back to the top of the Blogs section.

It's nice to see a site admin who has absolutely zero tolerance to buffoon-posts from buffoons. Give Robert a pat on the back, folks.

IMHO, this whole issue has got to be the biggest non-issue with Vista ever - and is near-perfectly timed to coincide with the end of 2007. Kinda nice to end the year with a whimper.

--ScottKin

Alright, so I published this over at Windows-Now.com (it does not display on the front page), I figured that I would post it here as well before my account here is deleted.

Alright, so after being harassed, flamed, and torn apart for the past ~24 hours via instant messenger and e-mail (which has resulted in me having to delete my personal e-mail account) about a post that I made on this website in regards to an issue that was found in the Windows Vista Explorer Search module, I've decided that I should come forth a little bit with you all.

Let's begin -- several years ago, during the Windows Code-name "Longhorn" era, I teamed up with Chris Holmes, someone who I consider to be a good friend, to work on several "guides" for tweaking the operating system, at the time I was only representing myself under the screen name "Nighthawk", although further into the Windows Vista beta I decided to use my actual name on the guides, as I felt it represented a step forward in professionalism in something that I enjoyed doing.

First and foremost, the reason that I posted the information regarding the flaw is because I was contacted by Microsoft stating that they would not be fixing the bug for Service Pack 1, which in my mind is a little bit boggling -- so I figured that a little bit of attention on this flaw would perhaps give someone over in Redmond a bit of a push to get this resolved, because it is a valid issue.

I've heard things such as "You're a [expletive] idiot for posting this", and "why the hell would you search for NOT Shortcut anyway?" This doesn't just apply to "NOT Shortcut", it applies to anything with "NOT".

You could search the folder for "NOT Music" or "NOT Peanuts" for all I care, it still crashes the process. I would have never thought that I would receive this kind of response to something like this, and I am truly disappointed. It seems as if some have reached a point where it doesn't matter if the operating system is full of bugs, as long as nobody speaks negatively about it, then all is well.

Unfortunately, I'm not the kind of person who will stand by and not take a stand for what I think is right. As an enthusiast and a human being, I cannot pretend and stand by to do what is "right" for the community, and no matter what the cost is, I cannot and will not continue with things in this state.

I was recognized for my contributions with the Microsoft MVP award in October for 2008, in the competency of Windows - Shell/User, which I felt was a real accomplishment and I was quite proud of myself. I've always had the passion to write -- and I focused primarily on Windows documentation, tweak guides, and tips & tricks. But unfortunately, after all of this, I've almost lost the inspiration and the passion to continue with my work as a Windows enthusiast. I've seen an extreme amount of distaste against what seems to be the truth lately, and that anything that doesn't go with the flow is automatically picked apart by fanboys and ego-maniacs.

At this point in time I would like to inform each and every one of you, and any of my readers out there, that I am pulling out from any current projects, tweak guides, and tips & trick guides, along with any involvement that I have with the community at this point in time. I'm going back to living my life, without being harassed over a blog post that I thought would be informative. With that being said, I do not know if I will be returning due to what seems to be a growing trend with "fanboyism" and the sheer amount of immaturity and disrespect that I have received in the past 24 hours.

To my fellow enthusiasts whom I have collaborated with over the years, including Chris, Mahmoud Al-Qudsi (author of EasyBCD), my friends at Microsoft Corporation, I wish you all the best and thank you for your assistance, guidance, and friendship. To Robert, the owner of Windows-Now.com, I would like to thank you for allowing me to host my information here on Windows-Now.com, and apologize if my previous blog post has caused you any grief.

I wish you all the best in the New Year and that you all take care of yourselves. Thank you for taking the time to read this entry.

Wow, I am completely astounded by this thread. All Kris did was post about an issue that was found in Windows explorer that Microsoft said they would not fix. He gave it a bit more of a public light in the hopes that it would kick someone over at Redmond in the ass and make them actually fix something for a change instead of senselessly closing the bug as "Not Reproducable".

The part that really gets me is that the same people who are flaming Kris about this, because it is not a "real issue", are the same people that bitch and moan all day long about vista being "****" and how it has so many issues. Umm hello? Anyone else seeing the irony here, or do you people just like to bitch for a living?

If there's one thing I've learned over the years, it's that you just have to stop caring about what other people have to say about you, because 99% of it is bull**** coming from immature little losers anyway. You guys may have succeeded in pushing out a great member of the community, I hope you're all happy now. I for one would not be pushed out like this because I don't pay any attention to senseless comments like this. I just stepped in now because this really needs to be addressed because it IS getting out of hand. Who CARES if you don't think it's an issue? In my book, ANYTHING that can crash a component of windows without adding a 3rd party plugin/application into the mix is a bug that MUST be fixed. Oh well, I don't even know why I'm wasting my breath on this, I'd probably make more progress talking to my walls.

Thanks for your kind words, Kris.

I know I speak for a lot of people here and in the rest of the online community when I say that no matter what transpired over the past couple of days everyone will certainly miss your contributions.

I'm shocked in disappointed in the reaction of many people as well, one would have expected a higher level of maturity when dealing with such issues, especially when they're being disclosed in good faith with the intention of getting them fixed, not flamebaited.

I wish you luck, wherever it is you choose to go from here.

Wow, I am completely astounded by this thread. All Kris did was post about an issue that was found in Windows explorer that Microsoft said they would not fix.

I think it's the sensationalist headline that most people have a problem with. It's not a serious flaw, by any means. A serious flaw (for example) would be an exploit that allows somebody to take over my computer remotely without me having to do anything. Not something that I type into the search field that crashes Explorer for a few seconds.

Steve.

Alright, so I published this over at Windows-Now.com (it does not display on the front page), I figured that I would post it here as well before my account here is deleted.

Instead of admitting that you blew it way out of proportion you choose to call everybody else fanboys? Comon, you could do better than that.

[Cross posted to Windows-Now]

We faced an issue with Vista. The issues? A few bugs being blown out of proportion, people thinking the beta of Vista was the final quality, people running Vista on CRAP hardware, and the most important; the blogosphere hating Vista.

So people started getting defensive of Vista against the stupid Mac heads and Linux heads. What happened here is that people got TOO defensive. We as a community are turning into the communities of zealotry, which we so despise, one of the principal reasons that we use Windows. We are becoming fanbois, and throwing our own under the bus.

What we all need to do is unite as a single community, drop these community wars, and start collaborating and trying to help Microsoft make a better operating system. Not say "IT IS PERFECT THE WAY IT IS!" I for one refuse to be part of a community where we must accept the OS as perfect, or be a "DUMB MAC FANBOI!" I am neither.

I have a genuine fear for where Windows and the community are going. Currently Microsoft seems to be trying to emulate Apple, and is doing so poorly. Microsoft is trying to follow a model that does not allow their community to make MAJOR change in their products. They are building up walls when they should be taking them down. As a community we are moving towards a model where we either must hate the OS to get Microsoft to change it or we need to defend it to the point where we spam one of the longest and smartest members of the Windows community, who deserves nothing less than our respect! It is absolutely disgusting to me that all these new comers to the beta scene think they have the right to harass one of the longest standing members of the community, and that they are smarter than someone who deserves nothing but respect. At this point today I am ashamed to call myself a part of what the Windows community has become, this Windows Community. Any of you who took part in the events of the last 24 hours, or any sort of extreme zealotry at all, should seriously rethink whether they should or deserve to call themselves Windows Enthusiasts.

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

    • No registered users viewing this page.
  • Posts

    • Apple raises MacBook and iPad prices as memory costs surge by Karthik Mudaliar Apple has raised the U.S. prices of several MacBook and iPad models, including the MacBook Neo, which it launched for $599 less than four months ago. The company’s cheapest laptop now starts at $699, while some MacBook Pro configurations have increased by $300. The changes affect the MacBook Neo, MacBook Air, MacBook Pro, iPad Air, and iPad Pro. Apple has not changed the hardware or storage included with these models, so customers are simply paying more for the same configurations. Here is how the new US pricing compares with the previous starting prices: Product Previous price New price Increase MacBook Neo $599 $699 $100 13-inch MacBook Air, 512GB $1,099 $1,299 $200 14-inch MacBook Pro, 1TB $1,699 $1,999 $300 16-inch MacBook Pro $2,699 $2,999 $300 11-inch iPad Air, 128GB $599 $749 $150 13-inch iPad Air, 128GB $799 $949 $150 11-inch iPad Pro, 256GB $999 $1,199 $200 13-inch iPad Pro, 256GB $1,299 $1,499 $200 The updated prices are already appearing on Apple’s U.S. online store. The MacBook Neo increase will probably attract the most attention. Apple introduced the laptop in March for $599, pitching it as a more affordable Mac for students and buyers considering Windows laptops or Chromebooks. It uses an A18 Pro processor and originally undercut Dell’s new $699 XPS 13 by $100. Following the increase, the two laptops now have the same starting price. The M5 MacBook Air has also lost the price Apple promoted when it launched in March. The 13-inch model arrived with 512GB of storage for $1,099, while Apple’s store now lists the MacBook Air range as starting at $1,299. The 14-inch MacBook Pro with an M5 chip and 1TB of storage has gone from $1,699 to $1,999. Apple has made similar changes to its iPads. The recently released M4 iPad Air, which launched at the same $599 starting price as its predecessor, now starts at $749 for the 11-inch version. The 13-inch version has risen from $799 to $949. The iPad Pro increases are larger in dollar terms. Apple’s 11-inch M5 iPad Pro now starts at $1,199, up from $999, while the 13-inch version has moved from $1,299 to $1,499. Both base models still include 256GB of storage. Apple blamed the increases on the rapidly rising cost of DRAM and NAND flash, which provide system memory and device storage. The company told Reuters that it had tried to shield customers from the increases but could no longer absorb them. “We have never seen a component price increase this much, this quickly,” Apple said. Tim Cook had already warned that price increases were coming. Cook said Apple’s existing component inventory had softened the immediate impact, but that higher memory costs would increasingly affect the company after the June quarter. Much of the pressure comes from the construction of AI data centers. Memory manufacturers are directing more production toward high-margin server products, leaving PC, tablet, and smartphone makers competing for the remaining supply. Apple has not said whether the new prices are temporary or whether further increases are planned. For now, the changes show that even Apple’s purchasing power has not been enough to keep the AI-driven memory shortage away from consumer devices.
    • Ventoy 1.1.16 is out.
    • This is a none story - these low volume Chinese models will always get new experimental features first because Apple and Samsung can't produce them in huge volume to meet demand.
    • Nvidia GeForce NOW gains support for Dark Scrolls, Empulse, and more by Pulasthi Ariyasinghe The final update of June for Nvidia's cloud gaming service GeForce NOW is now available, and it is touting support for six more games. The company is also drawing subscriber attention towards the summer sales kicking off across stores, so they can stock up on more cloud-supported titles. Of course, the Steam Summer Sale is the biggest promotion, which is kicking off later today. "Supported Steam games can be streamed across devices with GeForce NOW, making it easy to buy a game once, keep progress synced and pick up where the gameplay left off on PCs, Macs, handheld devices, phones, TVs and more," says the company. "In other words, the Steam Summer Sale brings the deals; GeForce NOW adds the flexibility." Don't forget that the GeForce NOW summer sale is still active as well. This limited-time offer drops the 12-month Performance membership from $99.99 to $64.99, saving members $35. At the same time, the 12-month Ultimate membership is currently going for $129.99, dropping the price by $70 from the original $199.99. Here are the games joining GeForce NOW's supported list this week: Dark Scrolls (New release on Steam, available June 22) SAND: Raiders of Sophie (New release on Steam, available June 22) Deer & Boy (New release on Steam, available June 23) EMPULSE (New release on Steam, available June 24) The Adventures of Elliot: The Millennium Tales (Steam) FATAL FURY: City of the Wolves (Steam) With the June expansions coming to an end, Nvidia should be announcing its July GeForce NOW plans next week. Keep in mind that, unlike subscription services like Game Pass or EA Play, a copy of a game must be owned by the GeForce NOW member (or at least have a license via PC Game Pass) to start playing via Nvidia's cloud servers. There is also a limit to how many hours subscribers can use the service per month.
    • Davinci Resolve 21.0.1 by Razvan Serea DaVinci Resolve is the world’s only solution that combines editing, color correction, visual effects, motion graphics and audio post production all in one software tool! Its elegant, modern interface is fast to learn and easy for new users, yet powerful for professionals. DaVinci Resolve lets you work faster and at a higher quality because you don’t have to learn multiple apps or switch software for different tasks. That means you can work with camera original quality images throughout the entire process. It’s like having your own post production studio in a single app! Best of all, by learning DaVinci Resolve, you’re learning how to use the exact same tools used by Hollywood professionals! DaVinci Resolve is the only post production software designed for true collaboration. Multiple editors, assistants, colorists, VFX artists and sound designers can all work on the same project at the same time! Whether you’re an individual artist, or part of a larger collaborative team, it’s easy to see why DaVinci Resolve is the standard for high end post production and is used for finishing more Hollywood feature films, episodic television programing and TV commercials than any other software. Davinci Resolve 21.0.1 release notes: Addressed multiple DNG and Apple ProRAW color issues. Addressed issue with automatic smart bins after deleting keywords. Addressed issue with multiple linked audio in media management. Addressed multiple Resolve FX issues in photo page. Addressed issue with key shortcut to switch viewer in photo page. More consistent creation of new photo albums. Addressed color thumbnail refresh for photo transform indicator. Transcription now honors project settings language. Improved face recognition in IntelliSearch. Addressed exported bins not retaining generator and title properties. Addressed ease control display and sensitivity issues. Addressed keyframe issue when copying clips with Fusion effects. Addressed keyframe refresh for Fusion effects in the edit page. Addressed issue with 3D renders in Linux with non-English locales. Addressed Fusion viewer color issue for some RCM settings. Addressed issue with saturation limits in Fusion gradient controls. Addressed Fusion display issues with dual screen layouts. Addressed issue with non-English character inputs in Linux. Disabling MultiMaster now disables trim blanking controls. Addressed crash in some scenarios with CineFocus. Addressed lag when toggling bypass grades and Fusion effects. Addressed occasional issue with Fairlight loudness meters. Addressed data burn display of good take tag in upgraded projects. Addressed project manager scroll lag for large project libraries. Support for Sony Alpha 7R VI ARW RAW stills. Support for decoding Affinity RGB 16-bit formats. Addressed a color issue with MainConcept H.265 HDR renders. Addressed a color issue with Windows native H.265 HDR renders. RemoveMotionBlur API now uses correct encode parameters. Addressed character limit consistency in GenerateSpeech API. General performance and stability improvements. Download page: Davinci Resolve 21.0.1 | 3300 MB (Free, paid upgrade available) Links: DaVinci Resolve Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      kinowa earned a badge
      First Post
    • Rookie
      krychek57 went up a rank
      Rookie
    • Grand Master
      Jaybonaut went up a rank
      Grand Master
    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      463
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      134
    4. 4
      Michael Scrip
      77
    5. 5
      Xenon
      77
  • Tell a friend

    Love Neowin? Tell a friend!