Monday, December 14, 2009

error code 0x80040905 with Google Earth installation

Solution 1:
  • Download and install this Windows installer Cleanup Utility:
  • After installation, Click "START" and run the utility. It will list all kinds of installations in your. Check "Google Earth" and select Remove.
  • Rerun the original Google Updater .exe

Solution 2:
  • Install Google Earth with this link:

Solution 3:
  1. Download 7-zip at:
  2. Download
  3. Right click the googleearth-Win-5.1.3533.1731.exe and scroll to 7-zip then choose open archive.
  4. When your in the 7-zip, open Program Files -> Google, then COPY the Google folder and paste it in C:\Program Files. Overwrite if any warning would appear. Do not copy anything else in googleearth-Win-5.1.3533.1731.exe archive, except the google folder.
  5. Go to the directory where the GOOGLE folder in drive C is located and open .exe.
Solution 4:
  1. Click "Start" > "Settings > "Control Panel."
  2. Double-click "Add or Remove Programs."
  3. Scroll down to find "Google Earth" and click it.
  4. Click Remove, then Yes, then Finish. Please note, this may result in an error, which can be ignored.
  5. Download and run the Windows Installer CleanUp Utility at
  6. Uninstall your version of Google Earth by selecting it from the list and clicking "Remove". Please see below for a list of possible entries.
  7. Upgrade to the latest version from our download link at

Monday, December 7, 2009

HTTP errors codes

100 Continue: the server has received the request headers, and the client should proceed to send the request body. If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient.
101 Switching Protocols: the requester has asked the server to switch protocols and the server is acknowledging that it will do so.
102 Processing (RFC 2518): As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost.

200 OK: Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.
201 Created: The request has been fulfilled and resulted in a new resource being created.
202 Accepted: The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
203 Non-Authoritative Information (since HTTP/1.1): The server successfully processed the request, but is returning information that may be from another source.
204 No Content: The server successfully processed the request, but is not returning any content.
205 Reset Content: The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.
206 Partial Content: The server is delivering only part of the resource due to a range header sent by the client. This is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
207 Multi-Status (WebDAV) (RFC 2518): The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.

300 Multiple Choices: multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.
301 Moved Permanently: This and all future requests should be directed to the given URI.
302 Found: redirect code[citation needed]. HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.
303 See Other (since HTTP/1.1): The response to the request can be found under another URI using a GET method. When received in response to a PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.
304 Not Modified: Indicates the resource has not been modified since last requested. The HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Utilizing this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then resent using more bandwidth of the server and client.
305 Use Proxy (since HTTP/1.1): Many HTTP clients (such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.
307 Temporary Redirect (since HTTP/1.1): the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.

400 Bad Request: The request contains bad syntax or cannot be fulfilled.
401 Unauthorized: Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.
402 Payment Required: The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code has never been used.
403 Forbidden: The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.
404 Not Found: The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
405 Method Not Allowed: A request was made of a resource using a request method not supported by that resource.
406 Not Acceptable: The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
407 Proxy Authentication Required.
408 Request Timeout: The server timed out waiting for the request. According to W3 HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time."
409 Conflict: Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.
410 Gone: Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed; however, it is not necessary to return this code and a 404 Not Found can be issued instead. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indexes.
411 Length Required: The request did not specify the length of its content, which is required by the requested resource.
412 Precondition Failed: The server does not meet one of the preconditions that the requester put on the request.
413 Request Entity Too Large: The request is larger than the server is willing or able to process.
414 Request-URI Too Long: The URI provided was too long for the server to process.
415 Unsupported Media Type: The request did not specify any media types that the server or resource supports.
416 Requested Range Not Satisfiable: The client has asked for a portion of the file, but the server cannot supply that portion.
417 Expectation Failed: The server cannot meet the requirements of the Expect request-header field.
418 I'm a teapot: The HTCPCP server is a teapot. The responding entity MAY be short and stout. This code was defined as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.
422 Unprocessable Entity (WebDAV) (RFC 4918): The request was well-formed but was unable to be followed due to semantic errors.
423 Locked (WebDAV) (RFC 4918): The resource that is being accessed is locked
424 Failed Dependency (WebDAV) (RFC 4918): The request failed due to failure of a previous request (e.g. a PROPPATCH).
425 Unordered Collection (RFC 3648): Defined in drafts of "WebDAV Advanced Collections Protocol", but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".
426 Upgrade Required (RFC 2817): The client should switch to a different protocol such as TLS/1.0.
449 Retry With: A Microsoft extension. The request should be retried after doing the appropriate action.
450 Blocked by Windows Parental Controls: A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.

500 Internal Server Error: A generic error message, given when no more specific message is suitable.
501 Not Implemented: The server either does not recognise the request method, or it lacks the ability to fulfil the request.
502 Bad Gateway: The server was acting as a gateway or proxy and received an invalid response from the downstream server.
503 Service Unavailable: The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
504 Gateway Timeout: The server was acting as a gateway or proxy and did not receive a timely request from the downstream server.
505 HTTP Version Not Supported: The server does not support the HTTP protocol version used in the request.
506 Variant Also Negotiates (RFC 2295): Transparent content negotiation for the request, results in a circular reference.
507 Insufficient Storage (WebDAV) (RFC 4918).
509 Bandwidth Limit Exceeded (Apache bw/limited extension): This status code, while used by many servers, is not specified in any RFCs.
510 Not Extended (RFC 2774): Further extensions to the request are required for the server to fulfil it.

Tuesday, November 24, 2009

Error code 8e5e0713 with Windows Live Messenger

Solution 1:
  • Check firewall settings.
    • With Windows Firewall:
      • Windows XP: Click Start, Control Panel, Windows Firewall.
      • Windows Vista or Windows 7: Click Start, Control Panel, Security, Windows Firewall, Change settings.
    • Switch to the Exceptions tab and check if there is a checked entry Windows Live Messenger. If there isn’t any, check the checkbox, adding Messenger as exception.
    • Click OK, and try to sign in to Messenger.
  • If it still doesn’t work, re-install Messenger.
    • Uninstall Messenger. With Windows XP:
      • Click Start, Control Panel, Add and Remove Programs.
      • A list of installed applications appears.
      • Click Windows Live Essentials, and choose Change/Uninstall.
      • A wizard for uninstalling Messenger opens.
    • With Windows Vista or Windows 7:
      • Click Start, Control Panel, Programs, Uninstall program.
      • A list of installed applications appears.
      • Click Windows Live Essentials, and choose Change/Uninstall.
      • A wizard for uninstalling Messenger opens.
    • Re-install Messenger (
    • After the setup, reboot your computer.
Solution 2:
  • Download a registry cleaner and install it.
  • Open the registry cleaner and scan you computer for free.
  • Click fix button and you done.

Saturday, November 7, 2009

Error 8000401a with MSN

Solution 1:
- Open Registry Editor
- search and delete "380689D0-AFAA-47E6-B80E-A33436FE3"

Solution 2:
- uninstall msn and download the new version

Solution 3:
- Download a 8000401a error repair tool,install this error repair tool.
- Click the Repair All Button.It will scan you pc for Free.
- Then click the Repair All Button again and your done.
- url of 8000401a error repair tool:…

Monday, September 28, 2009

Error Code 0x80070643


- Download this file:
- Run package to extract on the computer
- Go to directory that you extracted to, run startzune.exe
- Proceed with installation, following instructions (make sure you run the package as an admin.)

Wednesday, September 2, 2009

Error 81000306 with Windows Live Messenger

Solution 1:

Start/run type:
  • regsvr32 Softpub.dll
  • regsvr32 Mssip32.dll
  • regsvr32 Initpki.dll

Solution 2:

Solution 3:
  • Open the Messenger status website at . If you see a green check there, that means that the Messenger service is running, and you can continue with the next step. If the service is not running properly, check back later, until it is running. Continue with the next step then.
  • Delete the Windows Live Messenger proxy settings:
o Start Messenger.
o Open the menu next to your display name, and click Options.
o In the left column, choose Connection.
o At Connection settings, click the button Advanced settings.
o Delete the SOCKS entries.
o Click OK, then again OK.
o After you have deleted the proxy settings, retry to sign in to Messenger. If it still doesn’t work, continue with the next step.
  • If you are using Windows Vista, disable the auto-tuning feature:
o Click Start, All Programs, Accessories.
o Right-click the entry Command Prompt, and choose Run as administrator.
o When Windows prompts for your consent, click Continue.
o Now enter the following line in the command prompt, and press Enter:
netsh interface tcp set global autotuninglevel=disabled
o Note: using this command, you are disabling the Windows auto-tuning feature.
o Now retry to sign in to Messenger.
o If it still doesn’t work, re-enable the auto-tuning feature by repeating the preceding steps, yet typing this line instead:
netsh interface tcp set global autotuninglevel=normal
  • If you are using Windows Vista and a router (e.g. made by Linksys, Netgear, D-Link) to connect to the Internet, visit your manufacturer’s website to check for updates to your router’s firmware.

Wednesday, August 19, 2009

Error 80072745 with Windows Live Messenger

Solution 1:
If you are connected to the Internet through a router, remove the connection to the router. Then, directly attach the network or modem cable to the computer. This will help determine whether the issue is related to a firewall setting on the router. Try to sign in to Messenger after you connect to the Internet. If you can connect to Messenger after bypassing your router, the issue may be related to router settings. Try resetting your router (Note: This may revert your settings back to factory default settings and may delete all your custom settings.). Please contact your router manufacturer's Help documentation or customer support channels to determine how to reset your router or enable port 1863 through the router firewall.

Solution 2:
If you are signing in from a corporate environment, contact the network administrator to determine whether port 1863 is being blocked inside the network.

Solution 3:
If you have Zone Alarm with IM Security installed on the computer, turn off IM Security for Messenger:
- Right-click the Zone Alarm icon in the notification area, and then open the Control Center.
-Click IM Security or click Security to open the IM Security settings window.
-Click the Main tab or the Status tab.
-Slide the Protection Level slider to Off to turn off IM Security.
Note: This procedure will change the IM Security settings for any instant messaging programs that are installed on the computer.
-Sign in to Messenger again to determine whether the issue is resolved.

Solution 4:
if you have the NOD32, just disable the personal firewall, antivirus and antispam protection.
Sign in to msn then enable it again.

Solution 5:
AVG Antivirus+firewall do this: open AVG then double click to Web Shield. Choose "Instant Messaging" and remove the pipe from MSN Protection.

Friday, August 14, 2009

Error code 100

Horde mail:
Sendmail returned error code 100. The function popen ( is probably disabled in php.ini - removing the popen from disabled_functions solved the problem.
Another solution: [root@blabla]# setenforce 0 for disabling SELinux.

HTTP error code 100:
The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed.

Windows System:
System error code 100 means "Cannot create another system semaphore." This error code may also display as "ERROR_TOO_MANY_SEMAPHORES" or as the value 0x64.

Tuesday, August 4, 2009

Error 80200053 with Windows Vista Update


- Disable the AV program
- Go to Windows Update and get the updates
- Reactivate the Antivirus.

Tuesday, July 28, 2009

Error 10-FC12-0570 on Toshiba satellite

This error message means that the recovery utility was not able to read the data from the disc correctly, or wasn't able to write it to the hard drive.
The problem could be with the disc, the CD/DVD drive or the hard drive.


Try copying the second disc using another system. If it's impossible: order for a new disc. If you can copy it, try using the copy to do the restore.

Try using a third party disk checker to verify the problem, is or is not, with the hard drive.

The best way would be to load the Windonws Vista discs, format the pc and reinstall.
(Vista Recovery Boot Cd is available free by Microsoft). Download it burn the Image .iso and run that disc. That disc will not restore the OS: run diagnostics on the HDD; once disk check is completed and repaired, proceed with the Recovery disks that you have.

Tuesday, June 9, 2009

"AFS2K.SYS" Error Message Appears During Startup on HP Notebook


Download and install the latest version of the AFS driver for the HP Memories Disc Creator Software.
  1. Download AFS driver
  2. Click Software & Driver downloads .
  3. Select your operating system.
  4. Click afsinst.exe .
  5. Click Download now .
  6. When prompted to save or open the file, click Save .
  7. In the Save in: field, select Desktop .
  8. On the Desktop, double-click the afsinst.exe icon.
  9. The AFS installer will prompt you if a driver upgrade is available.
  10. Click Upgrade to install the latest driver. The upgrade process may take a few moments to complete.
  11. When installation finishes, click OK .
  12. If prompted, restart the computer.

Monday, May 18, 2009

Error 0xC00D11BA on Windows Media Player

Solution 1:
Open WMP, go to Tools, Options, Devices and wait till the window populates. Then highlight Speakers and click the Properties button.

Where it says, "Audio Device to Use", try changing to "Default Direct Sound Device". If that is already chosen, choose your soundcard from the dropdown list.

Solution 2:

Verify that a (most recent) sound device is installed on the computer; if not: just install one. Verify that the most current version of DirectX is installed.

Solution 3:
The speaker or sound device properties in the Player are configured incorrectly:

1) In the Media Player, on the Tools menu, click Options.

2) On the Devices tab, in the list of devices, click Speakers, and then click the Properties button.

3) On the Speakers tab, try changing the following properties:

- Select a different audio device for sound playback.

- If your problem is that you can't play audio CDs, clear the check box for the 24-bit audio option.

Error 8e5e05f6 in Windows Live Messenger

Solution 1:

1 - Exit Messenger.

2 - Change the Windows Explorer settings:

  • Right-click Start, and then click Explore to open Windows Explorer.
  • On the Organize menu, click Folder and Search Options.
  • Click the View tab.
  • In the Advanced settings list, select Show hidden files and folders under Hidden Files and Folders.
  • Clear the Hide extensions for known file types check box.
  • Click OK to close the Folder Options window.

3 - Delete the Contacts Cache folders:

  • Click Start, type “%USERPROFILE%AppDataLocalMicrosoftWindows Live Contacts”: delete all files in the folder.
  • Click Start, type “%USERPROFILE%Contacts”: delete all files in the folder

4 - Verify taht computer’s date and time settings are correct.

5 - Clear the Check for server certificate revocation option in Internet Explorer:
Start Internet Explorer.

  • On the Tools menu, click Internet Options.
  • Click the Advanced tab.
  • Under Security, clear the Check for Server certificate revocation (requires restart) check box.
  • Click OK.
  • Exit Internet Explorer

Solution 2:

Remove Messenger from the computer, restart and reinstall it.

Friday, April 3, 2009

Parsing error in file "C\programfiles\hp\digital imaging\bin\hpqscloc\1033.xml" on HP printers

This message is because Microsoft XML services are having a problem.

Solution to fix it:
  1. Uninstall All-in-One software.
  2. Restart the computer
  3. Install "Windows installer 3.0"
  4. Download and install "MSXML"
  5. Reinstall All-in-One software

Wednesday, April 1, 2009

Error 1000-0142 on hard drive

Hard drive has bad sectors.

  1. Boot from a Windows XP CD and choose Repair at the first prompt to get the recovery console. Type "chkdsk c: /p/r" at the prompt. Repeat until there are no errors found. Exit and reboot.
  2. Solution 1 doesn't work: also the hard drive must to be replaced.

Tuesday, March 17, 2009

Blackberry Storm: error code 0x80040fb3

Error Encountered 0x80040FB3, Check Documentation error appears during a wired synchronization.

Cause 1: One or more contacts in the Contacts application is missing information or has invalid characters in the First, Last, or Company name fields.
  • Resolution 1: Add text to the empty First Name, Last Name, or Company fields, or delete contacts with empty fields in the Microsoft Outlook address book.
  • Resolution 2: Remove invalid characters in the First, Last, or Company name fields.

Cause 2: There are attachments in the Calendar application.
  • Resolution: To resolve this issue, complete the following steps:
1. Turn off the synchronization for all other organizer applications except the Calendar in the Synchronization configuration window.
2. Turn on advanced synchronization logging and run the synchronization.
3. Provide the synchronization log files to your BlackBerry technical support representative for review.

Cause 3: There is corrupt Intellisync history.

  • Resolution: Reset the configuration of the synchronization. To do this, please perform the following:
1. Open the Desktop Manager.
2. Open the Synchronize application.
3. Click the Configuration tab (For Desktop Manager 4.5 - 4.7 click the Synchronization option under the Configure heading).
4. Press the Reset Configuration button.
5. Press Yes.

Cause 4: There is corrupt information in the organizer database.
  • Resolution: Clear the database for the affected organizer database.

Cause 5: Data within Microsoft Outlook is corrupted.
  • Resolution: Export the data as a CSV file, import it back in, and choose to overwrite the existing data. For instructions, visit Microsoft's support website and search for How to Import and Export Text Data with Outlook. Once this has been completed clear the assocaited database from the BlackBerry smartphone and try to synchronize again.

Cause 6: Corrupt data on the BlackBerry smartphone. (Clearing the addressbook using BlackBerry Desktop Manager does not resolve the issue)
  • Resolution: Perform a Wipe Handheld on the BlackBerry smartphone.

Error code 1603 with MSN Messenger

Solution 1:
- Try un-installing MSN Messenger completely from your computer and then re-install it: In the notification area, right-click the MSN Messenger icon, and then click Sign Out.
  • Click Start, and click Control Panel.
  • Click Add or Remove Programs, and then verify that Change or Remove Programs is selected.
  • In the list of programs, select MSN Messenger
  • Click Remove.
Solution 2:
- Click Start =>Run
- Type msiexec /unreg and press enter.
- Wait until it is finished.
- Go back to Start =>Run
- Type msiexec /regserver and press enter.
- Try to install MSN Messenger again; go to C:\documents and settings\all users\application data\microsoft\ Then select the folder "IdentityCRL" remove the folder. Run the setup.

Solution 3:
- Find C:\WINDOWS\WinSxS
- Rename the folder "InstallTemp" to "InstallTemp2".
- Rename the file "x86_Microsoft.Windows.Networking.Dxmrtp_6595b 6414 4ccf1df_5.2.0.4868_x-ww_212f7d9e" to "x86_Microsoft.Windows.Networking.Dxmrtp_6595b 6414 4ccf1df_5.2.0.4868_x-ww_212f7d9e2"
- Try to install again.

Solution 4:
If you are trying to install the Windows Installer package to an encrypted folder the error message will be displayed. Therefore, if you are doing so, change the installation folder to a folder that is not encrypted to resolve error 1603.

Solution 5:
If error 1603 is generated because the system account does not have full access permissions to the folder you are installing the package to, try this:
  1. Open the My Computer window.
  2. Select and right-click on the drive to which you want to install the Windows Installer package and then select Properties.
  3. Perform the following tasks on the Security tab.
    • On Windows 2000, ensure that the SYSTEM account is there in the Name box.
    • On Windows XP, ensure that the SYSTEM account is there in the Group or user names box.
  4. In case the SYSTEM account is not there, perform the following tasks to add it:
    1. Click the Add button.
    2. In the Select Users or Groups dialog box, select SYSTEM from the Name field and then click the Add button.
    3. Click the OK button.
  5. Next, select Full Control located under Allow, from the Permissions section and then click the Advanced button.
  6. Next, perform the following tasks:
    • On Windows XP, select the Replace permission entries on all child objects with entries shown here that apply to child objects check box for the SYSTEM account, and then click the OK button.
    • On Windows 2000, select the Reset permissions on all child objects and enable propagation of inheritable permissions check box for the SYSTEM account, and then click the OK button.
  7. After the permissions are applied, restart the installation for the Windows Installer package.

Wednesday, March 11, 2009

Inspiron 6000: Error Code 1000-0146

DST stands for Drive Self Test, if it fails the test it means your drive is failing.

  1. If you have access to a Windows CD: try to boot to the recovery console and run chkdsk /r. You can get it to boot, backup what you need, - then replace the drive.
  2. Another solution: Reinstall your OS.
  3. The hard drive is failed: get a new disk, install the OS, set the other as slave, and get the needed files.

Windows Live Messenger : Error code: 81000314

That's a server error.


- Wait and try again later ... !

Windows Live Messenger : Error Code 80072ee6


1 - Download the latest version of the DLL:
2 - Place the DLL in C:\Windows\System32

Monday, March 9, 2009

Yahoo Messenger: error code 40402

'Error code 40402' appears when you try to delete any addresses on "Yahoo IM".

  • Go in mail at "contacts" and delete them from there.
  • Change the contact details in Yahoo Messenger and it will save without any problem.

Error E70 on Affinity ATF7000E


The hot and cold water connections are reversed.

Thursday, March 5, 2009

Blogger: Error code bX-hq2u5m

1. Open the new template XML file in a text editor like WordPad

2. “Ctrl + F” and search for the word "widget id"

3. Replace the "b:widget id='Anything1'" to "b:widget id='Anything11'", you can replace the number into any number you want, but must be at least double digit, 1 to 11, 2 to 22.

4. Save the file. And upload the template either upload the xml file or cut and paste as usual.

Solution works for these errors to: "bX-bliced", "bX-y6cz0v", "bX-8dyqz0", "bX-si9ejx"...

Blackberry: "Error Encountered 0x80040ff8, Check Documentation"

Solution 1:
  1. Use BlackBerry® Desktop Manager to back up the data on the BlackBerry smartphone.
  2. Clear the Calendar database on the BlackBerry smartphone.
  3. Perform the synchronization again.

Solution 2:

Delete the Intellisync folder:
  • Close the desktop manager application.
  • Disconnect the BB from the computer.
  • Double Click on My Computer> Local Disk (C Drive>Documents and Settings>(username)>Application Data>Research In Motion>
  • Blackberry>Intellisync. (If the Application Data folder is not present, click Tools>Folder Options at the top of the screen.)
  • Click the View Tab, then click on Show Hidden Files and Folders.
  • Click Apply>Ok and continue through the remaining steps.
  • Delete everything within the Intellisync folder.
  • Launch desktop manager and attempt sync the device with the computer.

AOL: Error code C0FE180D with "Unable to download required content"

Cache and cookies must be deleted.

To clear the cache:
In the menus select Tools > Options > Advanced > Network - In the Cache section click "Clear Now".

To clear the cookies:
Select Tools > Options > Privacy - In the Cookies section click "Show Cookies..." to access the option for removing cookies.