XP Professional Windows Desktop Search 4 Indexing Will not Start [I40]

The short version for this bug report

Problem: After installing Comodo Internet Security (6.3.294583.2937) for the first time (no previous installation of Comodo CIS or Comodo firewall) on Windows XP Professional SP3, indexing for the Microsoft Windows XP powertool search program Windows Desktop Search 4.0 and for MS Office Outlook 2007 will not run and will not start from the Services menu in Windows XP

WORKAROUND:
Exit Comodo Internet Security->Reinstall the Windows Desktop Search 4.0 program (available freely from Microsoft…DO NOT uninstall the previous installation)->Start Windows Desktop Search 4.0 from the XP start menu

Service should be restored and on reboot indexing will autorun as normal, provided it has been selected to autorun, which it should be by default with the reinstall. If you had saved locations, they should still be there, but they will need to be reindexed. If you have Office Outlook 20XX, indexed searches will be restored as soon as your mail has been indexed…

The long version for this bug report

System:
HP DC7700
Intel E6400 core 2 duo 2.13 GHz
4 GB DDR 2
HD 1: Seagate Sata 250 GB
HD 2: Seagate Sata 250 GB
HD 3: Seagate USB 120 GB
Nvidia Quadro NVS290

On Windows XP Professional SP3. Windows Desktop Search 4.0 Indexer and Outlook 2007 indexed searches fail to start and generate error messages when the programs are started either as autoruns on boot or from the start menu of XP. Both searches yield no results. This began immedidately after installing Comodo Internet Security 6.3.294583.2937. Here are the error messages:

  1. Waiting to receive indexing status (System Tray notification)
  2. The instruction at “0x6001b35d” referenced memory at “0x0b6c1000”. The required data was not placed into memory because of an I/O error status of “0x00009c”. Click on OK to terminate the program. Click on CANCEL to debug the program. (Gray error message box)

Tried starting the service from the services dialog, but it will not turn on. Windows Search Indexing service turns on and then the error box pops up. It says it’s running, but it does not appear in Task Manager. Starting Indexing Service in the services dialog generates a different error message that says “Could not resume the Indexing Service on Local Computer. Error 1053: The service did not respond to the start or control request control in a timely fashion.” I also attempted to create exclusions in the Comodo firewall by using the “Allow Process” from the Firewall Task View of the main menu for the following processes (path not shown here…I can provide them if necessary):

cisvc.exe
WindowsSearch.exe
SeachIndexer.exe
SearchProtocolHost.exe
SearchFilterHost.exe
Outlook.exe

After closing and reopening the Services dialog in Windows XP, the Windows Search service, which did appear to have started is off, and the Indexing service is shown as paused. Starting them again is yields no positive results. Also tried disabling the firewall, testing, and then restarting and testing again, but still indexing will not run.

Even exiting Comodo Internet Security, testing, and restarting and testing does not resolve these issues.

WORKAROUND:
Exit Comodo Internet Security->Reinstall the Windows Desktop Search 4.0 program (available freely from Microsoft…DO NOT uninstall the previous installation)->Start the program from the XP start menu

Service should be restored and on reboot indexing will autorun as normal, provided it has been selected to autorun, which it should be by default with the reinstall. If you had saved locations, they should still be there, but they will need to be reindexed. If you have Office Outlook 200X, indexing will be restored as soon as your mail has been indexed…

This is certainly a strange issue. To better understand it, and since this is required for bug reports, please put it in the format provided in this post and attach all required files. This should give the devs enough information to replicate, and fix, this issue.

Thank you.

PM reminder sent.

For the time being I will move this to the Non-Format Verified board.

Topics in this board are rarely looked at by the devs, and even if they are it is unlikely the devs can fix the bugs reported. The reason is that putting bug reports in the required format, with the required files, ensures that the devs have enough information to understand and identify the bug. Thus, without this it becomes very difficult to replicate a bug such as yours.

To get your report forwarded to the devs please put this in the required format, and attach all required files.

If you have any questions please do not hesitate to ask.

Thank you.

Can you please check and see if this is fixed with the newest version (7.0.313494.4115)? Please respond to this topic letting us know whether it is fixed or if you are still experiencing the problem.

Also, note that all bug reports in the Non-Format section of the forum, which is where this report currently is, are mainly not looked at by the devs. Thus, if the bug you were experiencing is still not fixed please edit your first post so that it is in the correct format (found here, with all required attachments), so I can forward this to the devs and get this problem fixed.

Thank you.

PM sent.

Can you please check and see if this is fixed with the newest version (8.0.0.4337)? Please respond to this topic letting us know whether it is fixed or if you are still experiencing the problem.

Also, note that all bug reports in the Non-Format section of the forum, which is where this report currently is, are mainly not looked at by the devs. Thus, if the bug you were experiencing is still not fixed please edit your first post so that it is in the correct format (found here, with all required attachments), so I can forward this to the devs and get this problem fixed.

Thank you.

LOL…I still have this machine. Apparently it has been resolved with Comodo Firewall v10. I completely forgot about this and just began migrating to Comodo Firewall 10 a couple of weeks ago. On the same PC, there is no problem with Windows search 4.0, on XP SP3, not that anyone is going to care at this point :).

By the way, a testament to CFW and all the hard work of the development team. CFW is working extremely well on this old XP PC. I think this time I am going to have to stay with CFW. Although I wanted to do so before, I run complicated set ups in some instances, and configuration requirements were beyond available time allotments.

Apologies for forgetting about this all these months, and thanks to Comodo for sticking with XP all these years. Debates on securing the tattered relic have become much more interesting and enlightening…