Recommended Posts

You guys that are seeing crashes in the indexer, are you running Outlook and having that be indexed?

Does the crash occur at any specific time? Like during startup/shutdown or when you do a search? Does it only happen if Outlook is running or anything like that?

When you saw the error, did you let it send a crash report?

If you can tell me more about what you're seeing I can see if it's already been fixed for beta 2 or if it will be (or if it's something we don't know about).

Thanks.

You guys that are seeing crashes in the indexer, are you running Outlook and having that be indexed?

Does the crash occur at any specific time? Like during startup/shutdown or when you do a search? Does it only happen if Outlook is running or anything like that?

When you saw the error, did you let it send a crash report?

If you can tell me more about what you're seeing I can see if it's already been fixed for beta 2 or if it will be (or if it's something we don't know about).

Thanks.

Hi!

In my case, I don't even have outlook installed. The error sort of occurs randomly ( I was unable to identify the causes for this to occur). I sent the error report to microsoft a couple of times.

It happened when I just finished installing vista, in the first boot.

It happened when I tried to open explorer windows.

When I went into indexing options, it shown that the indexer was disabled (?)

I went into services mmc and disabled Windows Search and it all went fine.

I just don't have indexing at all in vista. :(

If you need more input, please feel free to contact me at tortulho_pt[at]hotmail.com

yea mine crashes everytime i access anything as my computer or control panel or anything basically really and i sent in a bug report for this as well.

Also how do you disable that user account control cause it is so anoying everytime you want to access anything with it poping up and asking for permission to continue.

yea mine crashes everytime i access anything as my computer or control panel or anything basically really and i sent in a bug report for this as well.

Also how do you disable that user account control cause it is so anoying everytime you want to access anything with it poping up and asking for permission to continue.

You can fix the crashing of the Search Indexer. Go to Control Panel, Regional and Language Options, then click on the Administrative tab and change the non-Unicode language to English (United States) and reboot. You will not have anymore crashes from the Search Indexer.

The user account control can be disabled from the Control Panel, User accounts, Change Security Settings and uncheck the UAC checkbox

I wonder what happened that is causing the indexer to crash :unsure: Wonder if they added features to it and that's what's causing the problems.

Lots of things change in the indexer frequently. For instance, in WDS 2.6.5 for XP we rewrote a large section of the indexer, and then had to take those changes and integrate them back up to the Vista codebase. There are also frequently changes elsewhere in Windows that affect us. I believe there are also lots of ongoing changes to the APIs for adding/removing indexer paths or checking whether a path is indexed.

I don't know the specifics of this problem but I'm looking into it.

Searchindex is really useless, basically anything like windows desktop search or google desktop search. By having two 10000 raptors in raid each disk with 8mb cache, that thing finds the file so fast that index is just pointless. If you have older machine with older hard drive, then searchindex is just system consuming.

Index search should be dropped. There are better ways to do it. Guess what? A new file system.....!!!!!

I never used index search in Windows XP, and not many people ever used it cause nobody found it useful. I guess Microsoft is trying to copy a lot of things from MacOS, but i have to be honest. MacOS is a crap...

Searchindex is really useless, basically anything like windows desktop search or google desktop search. By having two 10000 raptors in raid each disk with 8mb cache, that thing finds the file so fast that index is just pointless. If you have older machine with older hard drive, then searchindex is just system consuming.

Index search should be dropped. There are better ways to do it. Guess what? A new file system.....!!!!!

You're right that a new file system might be in order. But the rest of your post (except for the older system comment) is way off the mark. Instant-search is in high demand. And there's no way that your raptors (which not everyone has) can find files that fast. The current implementation of searching in Vista is horrendous, but it should improve quickly.

You're right that a new file system might be in order. But the rest of your post (except for the older system comment) is way off the mark. Instant-search is in high demand. And there's no way that your raptors (which not everyone has) can find files that fast. The current implementation of searching in Vista is horrendous, but it should improve quickly.

My desktop machine is not a server machine with 500Gb of data i need to seach for quickly. But, again if i have 500Gb of data (audio, video files), ona bad ass raid configuration hardware based will do perfectly. We are talking here about 0.5 - 1 seconds difference, and that means nothing.

By the way, there is one big problem Microsoft overlooked with the Windows desktop search. It has a big problem with razer gaming mouse or any similar type of mouse. By the default Windows desktop search stops indexing while you use the computer which includes the use of the mouse. With the razer mouse for example, even though you don't use it constantly sends the "call it impulses" so Windows desktop search thinks that OS is in use which means it never does actual indexing.

The razer mouse is based on the new technology, plasma mouse, unlike Logitech or any other brand which are optical.

A lot people use razer, but those are mostly gamers, and gamers don't use Windows desktop search :)

Either the company has to update firmware, drivers for their mouse, or Microsoft should fix the code.

Edited by freak_power

Just following up: It looks like this has been fixed for beta 2.

Searchindex is really useless, basically anything like windows desktop search or google desktop search. By having two 10000 raptors in raid each disk with 8mb cache, that thing finds the file so fast that index is just pointless. If you have older machine with older hard drive, then searchindex is just system consuming.

WDS is extremely useful on my machine with raptors in RAID 0. I'd be lost without it, for both files and e-mail.

Index search should be dropped. There are better ways to do it. Guess what? A new file system.....!!!!!

How is a new filesystem going to help you index data? What would be gained from bloating the filesystem with an index? And then you're limiting yourself since WDS can index any kind of data not just files. And what happens when you want to make changes to the index structure or update the schema? Require users to format their hard drives?

I never used index search in Windows XP, and not many people ever used it cause nobody found it useful. I guess Microsoft is trying to copy a lot of things from MacOS, but i have to be honest. MacOS is a crap...

Are you kidding? Indexed search is one of the most useful and powerful features in Vista. And it's not copied from MacOS - If anything, Cupertino copied that from us since we shipped it first.

My desktop machine is not a server machine with 500Gb of data i need to seach for quickly. But, again if i have 500Gb of data (audio, video files), ona bad ass raid configuration hardware based will do perfectly. We are talking here about 0.5 - 1 seconds difference, and that means nothing.

Well that's just BS so I won't even bother disputing your fake numbers there.

By the way, there is one big problem Microsoft overlooked with the Windows desktop search. It has a big problem with razer gaming mouse or any similar type of mouse. By the default Windows desktop search stops indexing while you use the computer which includes the use of the mouse. With the razer mouse for example, even though you don't use it constantly sends the "call it impulses" so Windows desktop search thinks that OS is in use which means it never does actual indexing.

The razer mouse is based on the new technology, plasma mouse, unlike Logitech or any other brand which are optical.

A lot people use razer, but those are mostly gamers, and gamers don't use Windows desktop search :)

Either the company has to update firmware, drivers for their mouse, or Microsoft should fix the code.

That's interesting feedback that I don't think I've ever heard before. Why would the Razer software be updating your cursor position when you're not moving the mouse? That won't just mess with WDS but lots of other things like power management, screensavers, etc.

Searchindexer crashes when your locale is not set to English (US)... Either set your location to US or disable the Windows Search service.

Searchindex is really useless

Actually I find indexed searches really useful and not for searching terabytes of data either. I often need to search 'inside' lots of files, like Word documents and PDFs. Copernic Desktop (the software I use in XP) can do this extremely quickly. It can also give me a preview of the document while highlighting the words I searched for... normal Windows search cannot do that.

Just following up: It looks like this has been fixed for beta 2.

WDS is extremely useful on my machine with raptors in RAID 0. I'd be lost without it, for both files and e-mail.

How is a new filesystem going to help you index data? What would be gained from bloating the filesystem with an index? And then you're limiting yourself since WDS can index any kind of data not just files. And what happens when you want to make changes to the index structure or update the schema? Require users to format their hard drives?

Are you kidding? Indexed search is one of the most useful and powerful features in Vista. And it's not copied from MacOS - If anything, Cupertino copied that from us since we shipped it first.

Well that's just BS so I won't even bother disputing your fake numbers there.

That's interesting feedback that I don't think I've ever heard before. Why would the Razer software be updating your cursor position when you're not moving the mouse? That won't just mess with WDS but lots of other things like power management, screensavers, etc.

The reason why so many people are lost with both files and emails is due bad directory/file management in Windows. I have 400Gb storage place on my server and i know where is the every file etc stored, and really don't need index search to find it. Having said that i barely use the regular search to find something. In order to fix directory structure in the windows i had to reorganize everything, manually and by using permissions. The problem is that system lets you save your files at any place you want, where overtime you get a such mess where i guess only index search can help you out to find the files you're looking for having the fact the station is used by multiple users. It's not hard to limit the actual user to save the files only into the my documents (whatever is called) folder which should be organized in such a way where the files with certain extension can go into certain folder. The directory structure and file organization didn't change since Windows 3.11 and Vista continues to use the same principles. :no:

And as a negative effect you have a problem of searching. Why would you need windows desktop search to search for file with extension, let's say *.doc if system saves those files under my documents and settings only in the system specified folder (call it wordDocs). System would know where to search for *.doc file which resides in one location namely directory and its subdirectories, safely can ignore rest of the XXXX folders on the hard drive. As a result you can really quickly find the file without using the indexing.

Also windows directory should not be visible to users, only to Administrator, as well as registry etc but that's part of security problem.

Windows Desktop search spends certain amount of time by doing indexing. And it's doing so often. The total amount i would spend to search for the files without using the windows desktop search is less then what windows desktop search spends by doing indexing meaning there is no real benefit, just different timing management which of course could be essential.

Razer software doesn't change the cursor position, but form some reason OS thinks that the mouse is active, so windows desktop search never starts because it thinks that the computer is in the use. I don't think it's Razer software problem, because i tried it using only Windows XP Generic Mouse driver. Maybe, it's just the way mouse works and OS doesn't handle it well. My screensaver and power management is disabled.

I tested razer mouse on two different machines, and symptoms were same. Windows Desktop Search never started indexing, even when i click Index now. After i click index now, it starts doing it for like 2-3 seconds and then stops. I switched the mouse to optical, and problem was solved. Of course I like my razer mouse more then windows desktop search:)

Edited by freak_power

The reason why so many people are lost with both files and emails is due bad directory/file management in Windows. I have 400Gb storage place on my server and i know where is the every file etc stored, and really don't need index search to find it.

That is completely and utterly nonsense. I have all of my stuff organized in a very convenient and sensible directory structure, and I still use WDS every day (and did even before I came out here to work on it). For example, it's so very much faster for me to type a few letters into the Deskbar than it is for me to navigate 6 folders deep to get to a song I want to play.

The directory structure and file organization didn't change since Windows 3.11 and Vista continues to use the same principles. :no:

The default directory structure has changed significantly in Vista, though pretty much everything has an analog from 2000/XP.

And as a negative effect you have a problem of searching. Why would you need windows desktop search to search for file with extension, let's say *.doc if system saves those files under my documents and settings only in the system specified folder (call it wordDocs). System would know where to search for *.doc file which resides in one location namely directory and its subdirectories, safely can ignore rest of the XXXX folders on the hard drive. As a result you can really quickly find the file without using the indexing.

That's great if you only ever want to filter by type. But happens when I want to see all the documents that John sent me? Now the system has to grep my WordDocs folder, my PowerPoints folder, my ExcelFiles folder, my entire e-mail store, and countless other places. What if I want to find all the documents with "Vista beta 2" in them? Same deal, except now you have to grep the contents of every file on the disk (or at least in my user profile or wherever I store stuff, plus all of Outlook) which is extremely slow.

What if you wanted to search for a list of people that have sent you meeting requests in the last month? Good luck doing that without an index.

Windows Desktop search spends certain amount of time by doing indexing. And it's doing so often. The total amount i would spend to search for the files without using the windows desktop search is less then what windows desktop search spends by doing indexing meaning there is no real benefit, just different timing management which of course could be essential.

WDS indexing doesn't take up any of your time. It'll spend some CPU cycles when you're idle, but there's a huge distinction there.

Razer software doesn't change the cursor position, but form some reason OS thinks that the mouse is active, so windows desktop search never starts because it thinks that the computer is in the use. I don't think it's Razer software problem, because i tried it using only Windows XP Generic Mouse driver. Maybe, it's just the way mouse works and OS doesn't handle it well. My screensaver and power management is disabled.

Then why do you think the problem is mouse related? It sounds like it's not.

I tested razer mouse on two different machines, and symptoms were same. Windows Desktop Search never started indexing, even when i click Index now. After i click index now, it starts doing it for like 2-3 seconds and then stops. I switched the mouse to optical, and problem was solved. Of course I like my razer mouse more then windows desktop search:)

Then that has nothing to do with your mouse. If you click the "Index Now" button, it disables the back-off engine, so WDS won't be paying attention to user activity or mouse movement. It will just go until the index is up-to-date. Once it's up-to-date it will reset back to it's normal operation where it only indexes during idle time. That is, unless you enable the "prioritize indexing" option in the WDS control panel, which causes the index to always be up-to-date instantly.

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

    • No registered users viewing this page.
  • Posts

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!