New
#1
Monitor falls asleep; Superfetch gone;Catalogue Corrupt
Hi, I am a novice with computers and lately my Desktop Computer has slowed and getting on to the internet takes forever. My game program diagnosed what's supposedly wrong below. Can anyone help me please, I am just a rookie. Thanks in advance.
Code:1202 - Source : SideBySide 1203 - Description : Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows. 1201 - Time : 11/6/2011 11:41:55 PM 1202 - Source : Windows Search Service 1203 - Description : The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt. Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) 1201 - Time : 11/6/2011 11:41:55 PM 1202 - Source : Windows Search Service 1203 - Description : The search service has detected corrupted data files in the index {id=4400}. The service will attempt to automatically correct this problem by rebuilding the index. Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) 1201 - Time : 11/6/2011 11:41:55 PM 1202 - Source : Windows Search Service 1203 - Description : The index cannot be initialized. Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) 1201 - Time : 11/6/2011 11:41:55 PM 1202 - Source : Windows Search Service 1203 - Description : The application cannot be initialized. Context: Windows Application Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) 1201 - Time : 11/6/2011 11:41:55 PM 1202 - Source : Windows Search Service 1203 - Description : The gatherer object cannot be initialized. Context: Windows Application, SystemIndex Catalog Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) 1201 - Time : 11/6/2011 11:41:55 PM 1202 - Source : Windows Search Service 1203 - Description : The plug-in in <Search.TripoliIndexer> cannot be initialized. Context: Windows Application, SystemIndex Catalog Details: Element not found. (HRESULT : 0x80070490) (0x80070490) 1201 - Time : 11/6/2011 11:41:54 PM 1202 - Source : Windows Search Service 1203 - Description : The plug-in in <Search.JetPropStore> cannot be initialized. Context: Windows Application, SystemIndex Catalog Details: The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801) 1201 - Time : 11/6/2011 11:41:54 PM 1202 - Source : Windows Search Service 1203 - Description : The Windows Search Service cannot load the property store information. Context: Windows Application, SystemIndex Catalog Details: The content index server cannot find a description of the content index in its database. Search will automatically attempt to recreate the content index description. If this problem persists, stop and restart the search service and, if necessary, delete and recreate the content index. (HRESULT : 0x80041181) (0x80041181) 1201 - Time : 11/7/2011 6:55:13 AM 1202 - Source : Service Control Manager 1203 - Description : The Superfetch service terminated with the following error: The system cannot find the file specified. 1201 - Time : 11/7/2011 2:50:02 AM 1202 - Source : Service Control Manager 1203 - Description : The Superfetch service terminated with the following error: The system cannot find the file specified. 1201 - Time : 11/7/2011 2:44:14 AM 1202 - Source : DCOM 1203 - Description : The server {3A185DDE-E020-4985-A8F2-E27CDC4A0F3A} did not register with DCOM within the required timeout. 1201 - Time : 11/7/2011 2:44:09 AM 1202 - Source : DCOM 1203 - Description : The server {209500FC-6B45-4693-8871-6296C4843751} did not register with DCOM within the required timeout. 1201 - Time : 11/6/2011 11:42:11 PM 1202 - Source : Service Control Manager 1203 - Description : The Windows Search service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. 1201 - Time : 11/6/2011 11:42:11 PM 1202 - Source : Service Control Manager 1203 - Description : A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect. 1201 - Time : 11/6/2011 11:42:11 PM 1202 - Source : Service Control Manager 1203 - Description : The Windows Search service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. 1201 - Time : 11/6/2011 11:42:11 PM 1202 - Source : Service Control Manager 1203 - Description : A timeout was reached (30000 milliseconds) while waiting for the Windows Search service to connect. 1201 - Time : 11/6/2011 11:42:11 PM 1202 - Source : DCOM 1203 - Description : DCOM got error "1053" attempting to start the service WSearch with arguments "" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} 1201 - Time : 11/6/2011 11:41:55 PM 1202 - Source : Service Control Manager 1203 - Description : The Windows Search service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ---------------------------------- End of file - 40324 Bytes
Last edited by Brink; 07 Nov 2011 at 00:05. Reason: code box
Quote