Learn The Secrets Steven Holdaway Use To Make Over $160,000 Every Single Month.
Powered by MaxBlogPress  
Blog Tips and News

This is the Blog Tips and News Section

General

Here you can find a general news

Web 2.0

Web 2.0 has AJAX, XHTML, API, RSS and etc

Web Services

Here is all the site provide services online

Windows Tips

All the tips for some version of windows

Home » OS Updates, Windows Tips

Problem on Window XP SP3

Submitted by User Imagerichardcqz on Saturday, 24 May 2008No Comment

Microsoft launched the new Windows XP SP3 in windows update, many users start to reporting that their network cards and previously crafted connections had mysteriously vanished from Windows after updating with the service pack. Besides that, the device managers window show empty screen and suspect is Windows’ registry, a directory that stores settings and other critical information, had been packed with large numbers of bogus entries.

Most users who posted messages on Microsoft’s XP SP3 support forum said that the errant registry keys — which started with characters such as “$%&” and appeared corrupted at first glance which is the section devoted to Sysmantec products. So some users will blame on the security company. After that, Symantec engineers had connected the current problem to a Microsoft file named “fixccs.exe.” According to information on the Web, fixccs.exe stands for “Fix CCS MaxSubkeyName mismatch,” and appears to be part of both XP SP3’s and SP2’s update packages that happen few years ago in two Microsoft Support Documents -  KB893249 and KB914450

“After you install Windows XP Service Pack 2 (SP2) on a Windows XP-based computer, the Device Manager window is blank or some devices no longer appear,” reads KB893249.

Fixccs.exe has also been linked to problems some users had installing early builds of XP SP3 late last year. In a support forum thread that started Dec. 22, 2007, Shashank Bansal, a Microsoft engineer helping users troubleshoot XP SP3 installation bugs, said: “This is a serious problem for us and we would like to investigate it to further depths. We would need help from all users on this forum for the same.” Bansal then asked users who had had trouble updating from XP SP2 to SP3 to identify the process that had hung or had hogged CPU cycles. “Look out for cscipt.exe or fixccs.exe,” he asked.

When asked earlier Thursday whether it had uncovered any more information about the disappearing Device Manager and the corrupted registry entries, Microsoft said it nothing new to add beyond the recommendation it made Tuesday: that users contact the company’s technical support desk if they have had problems upgrading to XP SP3.

Microsoft was not available for comment Thursday night.

Leave your response!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.

By submitting a comment here you grant this site a perpetual license to reproduce your words and name/web site in attribution.

ss_blog_claim=0242fe614a7b9e7af5c004582376d892