Skip to content

WDS 3.01 has shipped!

by Brandon on February 20th, 2007

Today we’ve released Windows Desktop Search 3.01 for Windows XP and Windows Server 2003.  This release includes many bug fixes and improvements based on user feedback received since the release of WDS 3.0 last fall.  Some users noticed the lack of UNC / network share indexing support in WDS 3.0 and insisted we put it back.  So we did!  The UNC / network share add-in is no longer a seperate downloaded and is included in WDS 3.01.

WDS 3.01 also brings back full Group Policy support (previously available in the WDS 2.6 Enterprise releases). 

Special congratulations to the indexer team, many of whom worked some pretty heavy hours through January to make sure this release had that extra layer of polish on it.  Thanks guys!  Now go home already!

Download links:

Windows XP 32-bit

Windows Server 2003 (32-bit)

Windows XP/2003 x64 Editions

Group policy ADM file is included in the package.  Run the installer with the /extract parameter to extract the contents directly.

There’s also an updated Advanced Query Reference for 3.x / Vista.

The WDS website and related docs are in the process of being updated as I write this.

From → Uncategorized

41 Comments
  1. John Murphy permalink

    And neither 3.0 or 3.01 seem to have “Help|About”.
    Good luck, everybody, trying to verify the version you have just installed.

    as pointed out here: http://brandonlive.com/2006/10/24/wds-30-has-shipped/#comment-2308

  2. Alex permalink

    Would like to bring a bug to your attention. It was reported on the forums some time ago but never acknowledged. It is still present in 3.01

    When indexing an Outlook Express store with a Hotmail account (http mail, not pop), if you leave OE running, after a little while searchprotocolhost.exe will pop up the following error message box:

    Outlook Express could not be started. The application was unable to open the Outlook Express message store. Your computer may be out of memory or your disk is full. Contact Microsoft support for further assistance. (0x80004005, 183)

    This can easily be reproduced on a fresh XP sp2 install. When the hotmail http account is removed the error goes away.

  3. Janson permalink

    Hi Brandon,

    Good to see you guys are listening and congrats to getting this out. Althoguh I see you have a link for the X64 versions I note that it doesn’t work currenlty. Looking at the KB article it only seems to reference 32-bit (x86) versions…. is a 64 bit version coming soon and will it included UNC support???

    Cheers

    Janson

  4. Joseph permalink

    Yes! Glad to see this is still being developed.

  5. Andrew permalink

    Good work, but here’s a few suggestions:

    a) Add an “About” dialog
    b) Update the WDS website – not coordinated with each other
    c) When I resize the white search results box, the buttons run against the box (just click the white search box on the taskbar, then once the floating window appears, resize it from the right and you’ll see what i mean)
    d) Allow us to sort results in the floating box
    e) Realign the search button to make it equally sized with the search box

    If that doesn’t make sense, email me.

    -Andrew

  6. Janson permalink

    I now have x64 version installed…. but… tell me its not so, no UNC/Network suppport….

    argghhh why is it that MS are trying to push the X64 platform and get there userbase moved to it when its treated as second class with regards to MS product releases???

    Its also very confusing to the userbase when essentially the same product relase comes out with different features. You are right, in that we weanted UNC/network support back in the base prodcut – but we wanted X64 support as well. so I guess waiting for 3.02…

  7. Carl permalink

    I love desktop search, but I still need to use the normal search companion in the explorer bar at times.
    The previous version of desktop search allowed me to turn this off, but I can’t seem to find the setting in the current version.

    Is there a registry key I can change to allow me to use the normal search companion from windows explorer?

    Carl.

  8. Stephen permalink

    Anyone got any ideas how to configure v3.01 via GPO/Registry to only index Outlook and My Documents? This setting seems to be missing from v3.01.

  9. Ivan Raide permalink

    Am I wrong, or is there still no UNC support for Vista64. Running the seperate UNC-FAT doesn’t work on Vista 64 (BTW)

  10. Sorry, still no UNC/FAT support for x64 OSes.

  11. Ivan Raide permalink

    Oh well, 🙁 good to know, thanks. Hopefully soon… Actually Brandon, didn’t you mention you were running Vista64 as well, (hopefully having an inside man with similar needs will get it done soon 😉 )

  12. Carl permalink

    With regards to my previous post, I was able to get a solution here:

    http://forums.microsoft.com/MSDN/showpost.aspx?postid=1275468&siteid=1

  13. Bill Fleming permalink

    3.01 has “enterprise deployment” and UNC capabilies, but as far as I can tell lacks the enterprise version’s (2.6.6) direct Intranet/SharePoint search capability.

    I had 2.6.6 running. Installed Office 2007, which replaced 2.6.6. with the dumbed-down 3.0. I uninstalled 3.0 and reinstalled 2.6.6. On restart the system notified me that an update to 3.01 was required. That was done, and again lost the Intranet search button.

    I need integrated search for Intranet (SharePoint 2003 running on Win Server 2003). Can that be achiwved with WDS 3.01?

  14. Mike permalink

    Brandon, you noted “The UNC / network share add-in is no longer a seperate downloaded and is included in
    WDS 3.01”. Do you know if the new version addresses the problem people were experiencing with
    WDS causing problematic file locks on shared drives in v2.6 (ie. http://support.microsoft.com/default.aspx/kb/927018/en-us)?

  15. Slightly OT, but does Vista’s search support searching network shares? I did not see an obvious way to add these when I tried.

  16. Brandon, I see that WDS currently doesn’t index the contents of EFS files. Under Vista, there’s an option that says “index Encrypted files” although I read somewhere this only applies to offline files. I understand that if the WDS service is running as System, then clearly it can’t read the contents of EFS files. Is there any work around? It seems like in my pre-Vista days, something I used indexed EFS, but whether it was Google desktop search, Lookout, or early WDS, I can’t remember since I used all of them at one point or another. I would appreciate your thoughts on this. Also, I look forward to trying out Start++ when it gets a little more mature. Thanks!

  17. Bryan permalink

    What about exclusion of Outlook folders? Did this make it back in? This “feature” (indexing every file in outlook) has made 3.x thus far USELESS for us — and as such we are still on 2.66.

  18. Nic permalink

    You are clearly proud of the WDS team – and I have to say that while the search speed doesn’t match that of Google, the indexing is significantly less intrusive and the results are well presented.

    However, the “extra polish” seems to have created a bug that means WDS 3.01 reindexes a large proportion of the index set on EVERY reboot. This is VERY annoying… especially as Outlook 2007 really does need WDS!

    P.S. As a response to comment 18 – I can’t see anyway in 3.01 to exclude a specific Outlook folder!

  19. Anon permalink

    I just upgraded to WDS 3.01 last night and I seriously wish I had backed up my computer just before doing it. It deleted the previous index and so must rebuild it again (which is expected), but it also got rid of the locations I had told it to index, as well as my deskbar shortcuts! That’s just not acceptable. I’m frustrated that I’ll have to spend a couple of hours figuring out how to add back all of the shortcuts I can remember, and I’ll have to experiment with the folders I’m indexing over time because I’ve got a lot of source code on my computer that likes to show up on every search.

    From looking in the options, I am surprised with the lack of features this version has. It seems that you can no longer set a custom default search provider, or tell it not to index while on battery. I gave http://www.live.com a good six months to impress me, but now I’m ready to go back to google (except for maybe image searching). Also, there are no longer tooltips in the instant search pane!

    Does anyone know where I can reinstall a previous version of Windows Desktop Search? Or is there anything I can do to recover this version to a state I’m willing to use? I’m sure if this was the first version I had ever tried, I’d have loved it, but I know there’s better, and I wasn’t expecting to be downgraded like this.

  20. Anon –

    It sounds like you were using a very old version of WDS. Since 2.6, you have not had to specify a custom web search provider. WDS uses your default browser and its default search provider (whoever you have configured it to be) to perform web searches.

    I’m not aware of the tooltip issue, I’ll have to look into that. Did the previous version you used even have the Search Pane integration? The versions with the Search Pane haven’t had the custom web search box (as I said above, it’s no longer needed).

    I thought Deskbar shortcuts would be migrated, strange that they were not. Depending on which version you had, you might find them under the Application Data \ Local folder on your machine (possibly in the Microsoft directory – they’re stored in a .ini file, called WindowsDeskbarShortcuts.ini or something like that).

  21. Nic –

    Google has an easier time seeming “faster” since they only return about 10 or 20 results on a page 😉

    As for reindexing data after a reboot – that is *sometimes* expected. Your filesystem should *never* need to be crawled for changes, and neither will Outlook 2007. That’s because the indexer can use the NTFS USN Change Journal to make sure it’s in sync, and because Outlook 2007 “pushes” items into the index and doesn’t need to be crawled.

    However, Outlook 2003 and things like UNC shares, IE history, or FAT filesystems will need to be crawled for updates. Otherwise the indexer has no idea what could have changed while the system was off or the service wasn’t running.

    That does NOT mean those stores are completely reindexed. It basically means that the indexer will check the folder timestamps to see if anything in them was updated since the indexer was last running. If so, it will then enumerate the files in that folder and look for what’s changed. Only then will it process the changed items. Overall it shouldn’t be a terribly long process and should go largely unnoticed for most users.

    Hopefully that makes some sense. If you believe you’re seeing something different (ie. the indexed item count is resetting to 0, or you believe it is reindexing files on your disk) then you may have encountered a bug that I’m not aware of. In that case, please e-mail me (brandon@brandonlive.com).

  22. Danny permalink

    Brandon,

    You mentioned that with WDS 3.01, you need to have Adobe Acrobat Reader 8.0 installed to search PDF’s. I do not have the Reader intalled, but I do have the full Acrobat 8.0 Professional installed on my system. Will that work as well?

    Thanks

  23. Alex permalink

    I am unable to install Windows Desktop search and get a “see logfile KB917013” message. I don’t know why
    it isn’t working and I can’t decipher the logfile to see what the issue is. Please advise.

    LOGFILE:
    00:00.000: ====================================================================
    00:00.000: INFO: Opening log for preliminary WDSSetup.exe actions
    00:00.000: Started: 2007/03/12 (Y/M/D) 17:51:49.093 (local)
    00:00.000: Command line:
    00:26.063: INFO: Closing down log for WDSSetup.exe logging
    0.094: ================================================================================
    0.094: 2007/03/12 17:52:15.359 (local)
    0.094: d:\d43739fe1cd9c2b42ba31385e1\update\Update.exe (version 6.3.4.1)
    0.109: WDS ********** InitalizeCustomizationDLL called.
    0.109: WDS ********** InitalizeCustomizationDLL: COMMANDLINE = /quiet /norestart /er
    0.109: WDS ********** InitalizeCustomizationDLL: UILEVEL = 0
    0.109: WDS ********** WdsUpd_AddStr of WDSUPD_CustStr_INSTALLDATE value 13584
    0.109: WDS ********** InitCustomStrings done.
    0.109: Hotfix started with following command line: /quiet /norestart /er
    0.109: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
    0.156: WDS ********** BeginInstallation called.
    0.156: WDS ********** BeginInstallation: Chancode
    0.156: WDS ********** BeginInstallation: PrevChancode
    0.734: In Function TestVolatileFlag, line 12013, RegOpenKeyEx failed with error 0x2
    0.734: In Function TestVolatileFlag, line 12045, RegOpenKeyEx failed with error 0x2
    0.734: DoInstallation: CleanPFR failed: 0x2
    0.734: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
    0.734: SetProductTypes: InfProductBuildType=BuildType.IP
    0.734: SetAltOsLoaderPath: No section uses DirId 65701; done.
    0.734: DoInstallation: SPCacheRoot (c:\windows\ServicePackFiles\ServicePackCache) directory does not exist, UseCache flag has been reset to 0
    0.750: DoInstallation: FetchSourceURL for d:\d43739fe1cd9c2b42ba31385e1\update\update.inf failed
    0.750: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB917013$
    0.750: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
    0.766: BuildCabinetManifest: update.url absent
    0.766: Starting AnalyzeComponents
    0.766: AnalyzePhaseZero used 0 ticks
    0.766: No c:\windows\INF\updtblk.inf file.
    0.766: OEM file scan used 0 ticks
    0.766: AnalyzePhaseOne: used 0 ticks
    0.766: AnalyzeComponents: Hotpatch analysis disabled; skipping.
    0.766: AnalyzeComponents: Hotpatching is disabled.
    0.781: AnalyzePhaseTwo used 15 ticks
    0.781: AnalyzePhaseThree used 0 ticks
    0.781: AnalyzePhaseFive used 0 ticks
    0.781: AnalyzePhaseSix used 0 ticks
    0.781: AnalyzeComponents used 15 ticks
    0.781: Downloading 0 files
    0.781: bPatchMode = FALSE
    0.781: Inventory complete: ReturnStatus=0, 31 ticks
    0.781: WDS ********** ConfirmInstallation called.
    0.781: Num Ticks for invent : 31
    0.781: Allocation size of drive C: is 4096 bytes, free space = 5737148416 bytes
    0.781: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
    0.781: Drive C: free 5471MB req: 35MB w/uninstall: NOT CALCULATED.
    0.781: CabinetBuild complete
    0.781: Num Ticks for Cabinet build : 0
    0.781: WDS ********** BeforeInstallOps called.
    3.781: ProcessDynamicStrings: InstallPathEnvVar for ProgramFiles returned C:\Program Files
    3.781: ProcessDynamicStrings: all %DynamicProgramFiles% replaced with C:\Program Files.
    3.781: ProcessDynamicStrings: CustomStringTable for CustStr_VERSION failed to find the string.
    3.781: FileInUse:: Added to Filelist: c:\windows\kb917013.cat
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\xmlfilter.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\en-us\wwres.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\wwres.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\wordwheel.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\en-us\windowssearchres.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\windowssearchres.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\windowssearch.exe
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\wdsview.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\wdsshell.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\wdsmkttools.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\en-us\uncres.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\uncres.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\uncph.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\uncne.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\uncdms.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\unccplext.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\tquery.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\en-us\tquery.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mui409\tquery.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\tquery.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\structuredqueryschematrivial.bin
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\structuredqueryschema.bin
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\srchadmin.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\en-us\srchadmin.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mui409\srchadmin.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\srchadmin.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\searchprotocolhost.exe
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\searchindexer.exe.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\en-us\searchindexer.exe.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mui409\searchindexer.exe.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\searchindexer.exe
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\searchfilterhost.exe
    3.781: FileInUse:: Added to Filelist: c:\documents and settings\all users\application data\microsoft\search\data\config\schema.txt
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\rtffilt.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\propsys.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\en-us\propsys.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mui409\propsys.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\propsys.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\propdefs.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\en-us\oephres.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\oephres.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\oeph.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\msstrc.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mssrch.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\en-us\mssrch.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mui409\mssrch.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mssrch.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mssprxy.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mssphtb.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\en-us\mssphtb.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mui409\mssphtb.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mssphtb.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mssph.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\en-us\mssph.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mui409\mssph.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mssph.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\mssitlb.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\msshsq.dll
    3.781: FileInUse:: Added to Filelist: c:\documents and settings\all users\application data\microsoft\search\config\msscolmn.txt
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\msscntrs.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\msscb.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\msnlred.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\msnlnamespacemgr.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\en-us\msnlextres.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\msnlextres.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\msnlext.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\msnldlps.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\msnldl.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\en-us\marketstrings.cfg
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\en-us\mapineres.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\mapineres.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\mapine.dll
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\idxcntrs.ini
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\idxcntrs.h
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\gthrctr.ini
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\gthrctr.h
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\gsrvctr.ini
    3.781: FileInUse:: Added to Filelist: c:\windows\system32\gsrvctr.h
    3.781: FileInUse:: Added to Filelist: c:\documents and settings\all users\application data\microsoft\search\data\config\gathrprm.txt
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\en-us\dsksrch.chm
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\deskbar.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\en-us\deskbar.cfg
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\dbsetup.dll
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\en-us\dbres.dll.mui
    3.781: FileInUse:: Added to Filelist: c:\program files\windows desktop search\dbres.dll
    3.844: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    3.953: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\kb917013.cat
    3.969: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    4.063: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\xmlfilter.dll
    4.094: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    4.203: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\en-us\wwres.dll.mui
    4.234: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    4.344: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\wwres.dll
    4.359: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    4.453: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\wordwheel.dll
    4.484: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    4.563: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\en-us\windowssearchres.dll.mui
    4.594: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    4.688: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\windowssearchres.dll
    4.719: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    4.813: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\windowssearch.exe
    4.844: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    4.938: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\wdsview.dll
    4.969: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    5.078: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\wdsshell.dll
    5.109: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    5.203: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\wdsmkttools.dll
    5.234: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    5.328: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\en-us\uncres.dll.mui
    5.359: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    5.453: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\uncres.dll
    5.469: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    5.563: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\uncph.dll
    5.594: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    5.672: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\uncne.dll
    5.703: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    5.813: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\uncdms.dll
    5.844: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    5.938: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\unccplext.dll
    5.953: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    6.078: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\tquery.dll.mui
    6.109: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    6.203: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\en-us\tquery.dll.mui
    6.219: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    6.313: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mui409\tquery.dll.mui
    6.344: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    6.438: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\tquery.dll
    6.453: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    6.547: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\structuredqueryschematrivial.bin
    6.578: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    6.672: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\structuredqueryschema.bin
    6.703: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    6.797: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\srchadmin.dll.mui
    6.813: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    6.938: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\en-us\srchadmin.dll.mui
    6.953: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    7.047: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mui409\srchadmin.dll.mui
    7.078: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    7.188: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\srchadmin.dll
    7.203: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    7.297: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\searchprotocolhost.exe
    7.328: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    7.406: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\searchindexer.exe.mui
    7.438: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    7.531: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\en-us\searchindexer.exe.mui
    7.547: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    7.656: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mui409\searchindexer.exe.mui
    7.672: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    7.781: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\searchindexer.exe
    7.797: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    7.906: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\searchfilterhost.exe
    7.938: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    8.031: FileInUse:: PrintTasksUsingModule: No tasks found using c:\documents and settings\all users\application data\microsoft\search\data\config\schema.txt
    8.047: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    8.156: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\rtffilt.dll
    8.172: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    8.281: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\propsys.dll.mui
    8.297: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    8.391: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\en-us\propsys.dll.mui
    8.422: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    8.516: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mui409\propsys.dll.mui
    8.547: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    8.656: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\propsys.dll
    8.672: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    8.781: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\propdefs.dll
    8.813: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    8.906: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\en-us\oephres.dll.mui
    8.922: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    9.031: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\oephres.dll
    9.063: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    9.156: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\oeph.dll
    9.188: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    9.281: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\msstrc.dll
    9.313: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    9.406: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mssrch.dll.mui
    9.438: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    9.547: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\en-us\mssrch.dll.mui
    9.578: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    9.656: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mui409\mssrch.dll.mui
    9.688: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    9.781: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mssrch.dll
    9.813: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    9.906: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mssprxy.dll
    9.938: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    10.016: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mssphtb.dll.mui
    10.047: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    10.141: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\en-us\mssphtb.dll.mui
    10.172: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    10.250: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mui409\mssphtb.dll.mui
    10.281: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    10.391: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mssphtb.dll
    10.406: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    10.500: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mssph.dll.mui
    10.531: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    10.625: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\en-us\mssph.dll.mui
    10.641: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    10.766: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mui409\mssph.dll.mui
    10.781: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    10.875: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mssph.dll
    10.906: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    11.016: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\mssitlb.dll
    11.031: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    11.125: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\msshsq.dll
    11.156: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    11.250: FileInUse:: PrintTasksUsingModule: No tasks found using c:\documents and settings\all users\application data\microsoft\search\config\msscolmn.txt
    11.266: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    11.359: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\msscntrs.dll
    11.391: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    11.484: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\msscb.dll
    11.516: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    11.609: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\msnlred.dll
    11.641: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    11.734: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\msnlnamespacemgr.dll
    11.766: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    11.859: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\en-us\msnlextres.dll.mui
    11.891: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    11.984: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\msnlextres.dll
    12.016: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    12.109: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\msnlext.dll
    12.125: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    12.219: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\msnldlps.dll
    12.250: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    12.344: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\msnldl.dll
    12.359: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    12.453: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\en-us\marketstrings.cfg
    12.484: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    12.578: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\en-us\mapineres.dll.mui
    12.594: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    12.688: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\mapineres.dll
    12.719: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    12.813: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\mapine.dll
    12.828: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    12.922: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\idxcntrs.ini
    12.953: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    13.047: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\idxcntrs.h
    13.063: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    13.172: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\gthrctr.ini
    13.188: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    13.281: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\gthrctr.h
    13.313: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    13.406: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\gsrvctr.ini
    13.422: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    13.531: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\gsrvctr.h
    13.563: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    13.656: FileInUse:: PrintTasksUsingModule: No tasks found using c:\documents and settings\all users\application data\microsoft\search\data\config\gathrprm.txt
    13.672: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    13.781: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\en-us\dsksrch.chm
    13.797: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    13.891: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\deskbar.dll
    13.922: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    14.016: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\en-us\deskbar.cfg
    14.031: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    14.141: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\dbsetup.dll
    14.156: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    14.266: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\en-us\dbres.dll.mui
    14.281: FileInUse:: IsTaskUsingModule: EnumerateLoadedModules64 failed: 0xc0000022
    14.375: FileInUse:: PrintTasksUsingModule: No tasks found using c:\program files\windows desktop search\dbres.dll
    15.375: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
    15.609: WDS ********** ArchivingComplete called.
    15.609: Num Ticks for Backup : 14828
    16.094: Num Ticks for creating uninst inf : 485
    16.109: Registering Uninstall Program for -> KB917013, KB917013 , 0x0
    16.109: Unable to get File Version
    16.109: Failed to copy spupdsvc.exe to system32
    16.125: WDS ********** EndInstallation called.
    16.125: WDS ********** FailedInstallation called.
    16.219: DeRegistering the Uninstall Program -> KB917013, 0
    16.219: Windows Desktop Search 3.01 Setup canceled.
    16.219: Update.exe extended error code = 0xf00d

  24. Anon permalink

    Hi Brandon,

    Thanks for the response. I didn’t realize that WDS now uses your internet browser’s default search provider for searching; I suppose that’s debatably better, and I have now changed my default search provider to what I want.

    Yeah, the instant search pane doesn’t show tooltips when I hover over any of the items, although it does if I hover over the search buttons. I don’t believe I had “Search Pane Integration”. By that, do you mean hiding the search puppy? I noticed that if I hit the Search button in windows explorer now, it has a WDS search thing. Brandon, have you ever considered having WDS maintain two indexes? I would like one of my documents and programs that will respond quickly, and another of my whole hard drive. The instant search pane could reference that one, and the Windows Explorer Search box could use the slower, more complete one.

    My deskbar shortcuts were indeed deleted. I looked at all *.ini files in Documents and Settings, and only the new WindowsDeskbarShortcuts.ini file was there.

    Is there a reason why there’s no choice to disable indexing while on battery power? I also noticed that there have been other modifications, such as the wording “Indexing speed has been reduced while you use your computer” rather than “Indexing is paused while you use your computer”.

  25. Chas permalink

    Hi Brandon, Quick question: Is there anyway to index multiple Outlook email boxes like older version (2.6). I need to index several shared email boxes.

  26. James permalink

    Hi Brandon,

    Strange thing – I have Office 2007 installed, along with WDS, on XP SP2. However, when I browse the list of IFilters (using IFilter Explorer), there is no IFilter installed for .DOC? Only .DOCX/DOCM?

    This seems a bit odd, are you able to shed any light? Does Office 2007 mean no pre-2007 IFilters? Because that would not make any sense..

  27. James permalink

    Regarding my post #27 – Resolved. It appears when I upgraded to Office 2007, for some reason OffFilt.dll was deleted (the IFilter registry entries for .doc, etc were luckily still intact, but just referring to a %windir%\system32\OffFilt.dll that no longer existed.

    Restoring this file to the version shipping with Office 2003 restored my .doc/.xls/.dot IFilter.

    I don’t know if this is a known issue, but just my experience, I’ll report it on Connect.

  28. Anon permalink

    Another issue I’ve noticed with WDS 3.01 is that it treats exe’s at a very low priority when returning results. I nearly always need to type myprogramname.exe in order for it to show up on the instant search pane (and at that point it’s the only thinig on the list).

  29. Anon permalink

    Unfortunately, WDS 3.01 is still not working very well for me. I’m getting tired of it rarely finding what I’m looking for, and am nearly ready to switch backto a previous version. Does anyone have any idea why this wouldn’t be working nearly as well as before? Is it because you can selectively index just the names of particular file types, and both the names and contents of different file types? Maybe this one is just set to index much less than the previous. That still wouldn’t explain why I have to type “microsoft visual studio 2005 kind:program” to even get Visual Studio onto the list… and with that, it’s still 12th on the list. The other programs are related to visual studio, but I would be typing their names in if I wanted to run them.

  30. Mark Opti permalink

    Thanks you very much for peace of garbage WDS3.01 that replaced nice WDS2.6
    By looking on the net I see that lots of people are going nuts with this one.

    I have on my PC WIndows XP SP2, Office 2003, SharePoint Designer 2007

    I have the same problem as other people describe. I had WDS 2.6 running just fine, but was stupid to install WDS 3.1 ( I was hoping to get latest and greatest but instead got a completly different product with seems drive lot of people go crazy). The MS KB says that it can be installed as upgrade ( i.e without removing 2.6)

    After that Outlook does not show up under indexing options. I did unistall/install. After that Outllok Expess showed up as an option but not Outlook.

    I do not understand what previous threads mean by saying “check Show Updates” in the Add/Remove program. If I do that , I see several dozens XP updates listed but none of them has WDS in the name.

  31. Anon permalink

    I think I’ve found where to download the installer of WDS 2.6. Hopefully, once I reinstally that version, it will be like it was before…

    http://www.microsoft.com/windows/desktopsearch/addresources/conversions.mspx

  32. Shree123 permalink

    is WDS 3.01 is officially released or in Beta version?

  33. I would like to add my frustations to other people ones with WDS 3.01. Every time I reboot the machine it takes 8 hours!!!!! to rebuild or re-check the index, this is not acceptable. I think you should look into this issue and find a better solution.

  34. Jeff permalink

    There is a problem with the policies for “exclude certain paths” as well as the “default indexed paths” and “default included paths” when it is applied to mapped network drives. When you apply the policy, a new drive selection is added to the list of available drives to index and it is grayed out. However, the original drive remains and can still be checked and indexed. I have tried numerous formats for example S:, file:///S:, etc. Furthermore, there is no explanation within the policy of how you are supposed to enter the excluded or included entries. If they are not entered correctly, the entire list of available indexed paths disappears. I would really like to get this working right so I can roll it out for my users.

  35. Jerry Sully permalink

    I cannot seem to locate the .adm file. I have extracted the contents using the /extract parameter, and everything seems to extract fine, but no .adm file is present in the directory. Where can I find this?

  36. Can’t get it off my machine. Says it creates an uninstall directory (but it doesn’t). Can someone please release a removal tool for this software?

  37. WDS absolutely does create an uninstall directory. If you deleted it (for example, by deleting all Windows Update uninstallers, as some ill-advised “tweakers” often do), you will have a lot more difficulty in uninstalling WDS. Are you certain it isn’t showing up in Add/Remove Programs? Did you check the “Show Updates” box? Are you certain you or anyone else didn’t delete any of the NtUninstall directories? (or use some tweak program or disk “cleaner” that may have done that?).

  38. Goran permalink

    WDS complains cannot uninstall. And Yes I have deleted all kbuninstall folders.
    If I have a full disk, and I don’t see a reason to uninstall the old fixes, I gladly delete the 200 or so uninstall folders to get more disk space. This is the first time I have seen a problem coming from that. Perhaps the design could have been somewhat different, either with all these uninstall folders or with wds?
    Anyway I think we need either a proper remove tool or an WDS upgrade, handling it all in one sweep.

  39. jukka permalink

    If I installa WDS on multiple workstations and they all just index one network share, shoud I also put the index to that same network share or use own index on every pc??
    why?

Trackbacks & Pingbacks

  1. Arian Kulp's Blog
  2. Paul Paradise » Blog Archive » Windows Desktop Search 3.01 Released

Leave a Reply

Note: XHTML is allowed. Your email address will never be published.

Subscribe to this comment feed via RSS