registry corruption windows xp sp2 Results


Sponsored Links:



I have some relatives who run a PC with Windows XP SP2, and Internet Explorer 7.
Up until Thursday night, all was well and everything functioned OK.. Then




There have been a number of installation errors of the July 27th Office 2003 Updates and other Office version updates, particularly Office 2003 SP1 remedied by Office resource kit tools and other tools like the Windows Installer Cleanup Utility, and I'm pasting this information that has come up from Sloan Crayton [MS] who has been generously helping and providing some useful information on using these Office tools to help with install/setup problems. Because it involves information I have not seen anywhere, including MSKB, MSDN, Technet or Windows SP2/MSI 3.0 articles and good artifcles on System Restore, I'm pasting some of it he

__________________________________________________ _____

After running the Installer Clean utility to remove remnants of OfficeXP, now if I try to update Office 2003 Pro from the website, this is EXACTLY what I get:

The Office Update site is unable to check for updates on this
computer. This may be happening because of one of the following
reasons:

You do not have administrative privileges for this computer.

There is a network problem and the detection catalog used by the
Office Update site failed to download. Go back to the Downloads home
page and try running detection again.

Windows Installer patch files (.MSP files) from previously applied
Office updates are missing from the WindowsInstaller hidden
directory on your computer. MSP files are stored on your computer
after update installation completes because they need to be referenced
for future update operations. If the files are missing you will not be
able to apply Office updates. You may also be unable to uninstall
Office products as a result of the same problem. Please contact
Microsoft Product Support Services for assistance.

You installed Office updates in the past and then upgraded from
Windows Installer version 1.0 to Windows Installer version 1.1. For
more information see the KB article Windows Installer May Prompt for
Install Source if Unavailable.

Search for Office updates in the Download Catalog

The Problem With System Restore and the Windows Installer Corrected by Windows Installer 3.0

(Fixing the Problem but not Fixing the Registry Once It's Corrupted):

__________________________________________________ ____________

Windows System Restore will corrupt the Windows Installer registry
information for Office (and other applications). Windows Installer 3.0
(included in Windows XP SP2 when it ships) will fix this bug

The use of Windows System Restore is one of the known causes. Windows Installer 3.0 which is included in Windows XP SP2 fixes this problem (but will not fix it once it's broken).

You will need to use the Windows Installer Cleanup Utility to remove the
Windows Installer registry information for all installed Office products.
Then you'll need to install Office 2003 again and then install any service
packs and public updates.

This is documented in the KB article at
http://support.microsoft.com/default...b;en-us;304498.

Sloan Crayton
Microsoft

__________________________________________________ _______________

Best,

Chad Harris




I've reported about my SP2 installation failure already:
Subject: SP2 Disaster for XP here; Not solved yet.
The previous threads appear dead; I'm continuing my story here.

Briefly, I can't boot form the drive that I installed SP2 to.
To remedy the problem, I tired...

A. system restore
Result: Didn't help

B. uninstalling SP2 using
"1. At the command prompt in Recovery Console, type the following lines.
Press ENTER after each line.
cd $NtServicePackUninstall$Spuninst
batch spuninst.txt
exit
"
Result: it said
"The system cannot find the file or directory specified"
(System Restore probably already removed the file.)

C. A repair install of Win XP
Result: error code, a stop code, 0x0000007B (4 parameters)
http://support.microsoft.com/default...b;en-us;324103
The solution has to be in resolving this.

D. I called and emailed MS, Phone-in Case # SRX040824605385

Result: email back saying it was a duplicate case to the phone-in case,
so they were closing the email case.

So I'm ready to tackle the 0x0000007B problem. I'm going to try the
driver issue possibility first.

On http://support.microsoft.com/default...b;en-us;324103
"Device Driver Issues
You may receive a "Stop 0x0000007B" error message in the following
scenarios:

A device driver that the computer boot controller needs is not
configured to start during the startup process.

A device driver that the computer boot controller needs is corrupted.

Information in the Windows XP registry (information related to how the
device drivers load during startup) is corrupted.

Windows XP requires a miniport driver to communicate with the hard disk
controller that is used to start your computer. If Windows XP does not
supply a device driver for your controller or if Windows XP is using a
corrupted or incompatible driver, you must replace the driver with a
valid copy that is compatible with your controller and Windows XP.

During the first phase of the Windows XP installation, Setup displays
the following message at the bottom of the screen:
Press F6 if you have to install a third-party SCSI or RAID driver.
Press F6 and then follow the instructions to install a mass-storage
device driver from your Original Equipment Manufacturer (OEM). For
additional information about using F6 to load an OEM device driver to
support, click the following article number to view the article in the
Microsoft Knowledge Base:
314859 Limited OEM driver support is available with F6 during Windows XP
Setup

To determine if your hard disk controller is compatible with Windows XP
and to obtain information about drivers that are included on the Windows
XP CD-ROM or that are available for download, see the latest Windows XP
Hardware Compatibility List (HCL). For additional information about the
latest Windows XP HCL, click the following article number to view the
article in the Microsoft Knowledge Base:
314062 The latest Windows XP hardware compatibility list

If your hard disk controller is not listed on the HCL, contact the
manufacturer of your computer, system board, or hard disk controller for
information about the availability of a driver. Microsoft does not
guarantee that a resolution is available for non-HCL equipment. For
additional information, click the following article number to view the
article in the Microsoft Knowledge Base:
315239 Microsoft support policy for hardware that does not appear on the
Windows HCL

If the System hive in the Windows XP registry is corrupted, Windows XP
may not be able to load the miniport device driver that the boot
controller requires. To resolve this issue, restore a registry backup.
For additional information about restoring a registry backup, click the
following article number to view the article in the Microsoft Knowledge
Base:
307545 How to recover from a corrupted registry that prevents Windows XP
from starting "

I have another working non-SP2 Win XP drive that I'm using to operate. I
can attach, as a slave, the problem drive and see everything.

What does "miniport driver" mean? is that different from a regular
driver?

--
*********************
* Nehmo Sergheyev *
*********************




I've reported about my SP2 installation failure already:
Subject: SP2 Disaster for XP here; Not solved yet.
The previous threads appear dead; I'm continuing my story here.

Briefly, I can't boot form the drive that I installed SP2 to.
To remedy the problem, I tired...

A. system restore
Result: Didn't help

B. uninstalling SP2 using
"1. At the command prompt in Recovery Console, type the following lines.
Press ENTER after each line.
cd $NtServicePackUninstall$Spuninst
batch spuninst.txt
exit"
Result: it said
"The system cannot find the file or directory specified"
(System Restore probably already removed the file.)

C. A repair install of Win XP
Result: error code, a stop code, 0x0000007B (4 parameters)
http://support.microsoft.com/default...b;en-us;324103
The solution has to be in resolving this.

D. I called and emailed MS, Phone-in Case # SRX040824605385

Result: email back saying it was a duplicate case to the phone-in case,
so they were closing the email case. (Thursday morning will be 48 hrs
since I called. They said they'd be in touch by that time.)

So I'm ready to tackle the 0x0000007B problem. I'm going to try the
driver issue possibility first.

On http://support.microsoft.com/default...b;en-us;324103
"Device Driver Issues
You may receive a "Stop 0x0000007B" error message in the following
scenarios:

A device driver that the computer boot controller needs is not
configured to start during the startup process.

A device driver that the computer boot controller needs is corrupted.

Information in the Windows XP registry (information related to how the
device drivers load during startup) is corrupted.

Windows XP requires a miniport driver to communicate with the hard disk
controller that is used to start your computer. If Windows XP does not
supply a device driver for your controller or if Windows XP is using a
corrupted or incompatible driver, you must replace the driver with a
valid copy that is compatible with your controller and Windows XP.

During the first phase of the Windows XP installation, Setup displays
the following message at the bottom of the screen:
Press F6 if you have to install a third-party SCSI or RAID driver.
Press F6 and then follow the instructions to install a mass-storage
device driver from your Original Equipment Manufacturer (OEM). For
additional information about using F6 to load an OEM device driver to
support, click the following article number to view the article in the
Microsoft Knowledge Base:
314859 Limited OEM driver support is available with F6 during Windows XP
Setup

To determine if your hard disk controller is compatible with Windows XP
and to obtain information about drivers that are included on the Windows
XP CD-ROM or that are available for download, see the latest Windows XP
Hardware Compatibility List (HCL). For additional information about the
latest Windows XP HCL, click the following article number to view the
article in the Microsoft Knowledge Base:
314062 The latest Windows XP hardware compatibility list

If your hard disk controller is not listed on the HCL, contact the
manufacturer of your computer, system board, or hard disk controller for
information about the availability of a driver. Microsoft does not
guarantee that a resolution is available for non-HCL equipment. For
additional information, click the following article number to view the
article in the Microsoft Knowledge Base:
315239 Microsoft support policy for hardware that does not appear on the
Windows HCL

If the System hive in the Windows XP registry is corrupted, Windows XP
may not be able to load the miniport device driver that the boot
controller requires. To resolve this issue, restore a registry backup.
For additional information about restoring a registry backup, click the
following article number to view the article in the Microsoft Knowledge
Base:
307545 How to recover from a corrupted registry that prevents Windows XP
from starting "

I have another working non-SP2 Win XP drive that I'm using to operate.
The drive I installed SP2 to is currently attached as a slave. I can see
everything on the drive.

What does "miniport driver" mean? is that different from a regular
driver?

--
*********************
* Nehmo Sergheyev *
*********************




Anyone have an idea o=ADn how to repair the Windows XP Pro=20
SP2 registry? Have been using SP2 for about 2 weeks, but=20
whenever I now try and start the computer, I get the=20
following error message:

"Windows could not start bcause the following file is=20
missing or corrupt:
WindowsSystem32ConfigSystem
You can attempt to repair this file by starting=20
Windows Setup using the original Setup CD-
ROM. Select "r" at the first screen to start repair."

Tried this without success. Then went to Microsoft.com=20
Microsoft Knowledge Base Article -=20
307545, "How to recover a corrupted registry that prvents=20
Windows XP from starting."

I tried this cut and past method of substituting the=20
files in the c:windowsrepair directory (system,=20
software, sam, security, and default) for those in the=20
c:windowssystem32config directory. But o=ADnce again,=20
instead of starting, I receive the error message noted=20
above.

Any assistance will be appreciated.

Sincerely,

Ken




I have Ad-Watch monitoring installed which alerts me to any attempt to change registry settings. It has suddenly started alerting me to attempts to make changes on boot up. I recently installed Win XP SP2 and also Omnipage 14 so the requests may be left over from temp files that have not been cleaned up, a corrupted install or something. Here is a typical example:

Key: Software/Microsoft/Windows/CurrentVersion/RunOnce
Value: OE-WMPWMP7_Install_0
Data: CWindowsNFunregmp2.exeMigrateLibrary

Another Data setting that also comes up is:
Data: CWindowsSystem32msnnet??(can't read my writing!).dllsystem32"blackbox.dll"

Any ideas on how I can a) gett rid of these requests and [img]/forums/images/smilies/cool.gif[/img] is it anything more sinister than a corrupted install or whatever?

TIA

Richard




I have a similar problem on 2 computers. One is a bad install on XP so I did a second install and put it in a different folder and deleted the other Windows folder. However, on startup I am presented with 2 choices, one the good copy and one the corrupted copy. It defaults to the good copy, but I would like to be able to remove the corrupted copy. I have run JV16 Registry Cleaner and that doesn't do it. Also on a second computer I installed XP over 2000. I wanted to get a command prompt at startup and delete 2000 first, but when I hit F8 twice, I got that I could do a safe mode with command prompt. Well, I got safe mode but could never get the command prompt, so I finally installed XP anyway. I am wondering whether there is any way to get rid of the 2000 copy. Any ideas appreciated.




Edited by HansV to provide link to post by typing [post#=401213] - see Help 19.

I have followed the discussion in thread post 401213, and read the references, but still have a problem setting the desired pagefile size.

Using Win XP Pro SP2, 1Gb memory, System Drive C, Data Drive D (logical), both FAT32, logged on as Administrator. As I am a little low on space on the C drive, I would like a page file around 512MB, rather that the 1.5Gb windows wants to set.

1. If I allow the system to set the size on C, it gives Recommended 1533 / allocated 841, and parameters of cagefile.sys 0 0 in the Registry Memory Management key

2. If I set the Custom Size to 512 / 512, it gives recommended 1533 / allocated 1533, and the registry shows cagefile.sys 512 512

3. When I set No Page file on C and 512 / 512 on D, it gives recommended 1533 / allocated 512, and shows dagefile.sys 512 512 in the registry.

For some reason, I cannot make the size 'stick' on drive C. I have tried muultiple reboots and combinations of different sizes on C and D. I do not want to use D for the page file, as there can be problems with backup programs such as DriveImage / PartitionMagic, if the System drive gets 'separated' from the drive with the pagefile.

I also have this problem on another drive with a 'clean' WinXP install, so do not think it is local registry corruption????




Hi folks,

I have a weird problem with PowerPoint. It opens correctly and can display an existing presentation just fine, but if I try to change the presentation slides template by clicking Format | Slide Design, I get the error message:
"Microsoft Office PowerPoint can't display the template used in this document. Microsoft Office PowerPoint cannot install the necessary files due to Windows installer error 1606. Feature ID not registered."
Weirdly, this is displayed a consistent 66 times (I can be very persistent sometimes) and then it goes ahead and displays the various design template choices anyway (there are 44) and allows me to apply any of them.

I've tried de-installing both Office and the Windows Installer, running Registry Mechanic, re-installing Installer and then Office (and then SP2), but to no effect at all. Running Windows XP Pro SP2, Office SBE 2003 SP2, Norton AV, Zone Alarm, Counterspy, etc.

I had a very similar problem with Word (the same message popped up four times in a row whenever I opened Word, which then did display a blank document created with the normal.dot template it said it couldn't display), and it turned out to be a corrupted normal.dot template. Renaming the existing one and letting Word build a new one cured that; is there a similar exercise that would help here?

Any ideas?

Regard

Jon Inge




I have read several threads on this subject, but I need some help. My son's computer is rebooting continually. I was able to stop the auto-restart to see the BSOD:

Stop: c0000218 [registry file failure]
The registry cannot load the hive (file) system root system32 config software or it's log or alternative is corrupt, absent, or not writable.

I have attempted to load the last known good configuration and that doesn't help.
Safe mode hangs at mup.sys
I tried the Repair from the Recovery Console and after telling it R and which directory windows is in, it reboots and starts all over again.

What next....?

--KZ




I found that certain Word documents which contain upwards of 20 or 30 small tables (2 or 3 rows, 4 or 5 columns, apiece), work fine as long as a user is working withing the document originally in Word 2007, but after saving as a DOC and re-opening, the user is prompted to do an "Open and Repair" and there is frequent corruption around a table within the document. Usually there are missing end-of-cell or end-of-table markers (according to the Repair message box).

We are using the DOC format instead of DOCX.

Is something known to be systematically worse about Word 2007 saving to DOC format instead of DOCX?

All of the PCs in my firm are configured with Windows XP SP3, and Office 2007 SP2. For reasons of compatibility with other systems, we work with the following two Registry values set:

HKCUSoftwareMicrosoftOffice12.0WordOptions
DefaultFormat REG_SZ "doc"
CompatMode REG_DWORD 00000001

These cause MS Word 2007 to be in a 2003 "compatibility mode" and to save files in a DOC format by default.

Anyhow upon reopening a DOC document, the message from Word saying I need to do an 'Open and Repair' is happening a lot. Something like 50% of the time (for documents containing 20 to 30 tables).

I recall that with MS Excel 2007 there was an issue saving to the XLS format and seeing all cells turn to #VALUE and a message appearing saying "File error: data may have been lost." This only occured with Excel 2007 saving as XLS and inconsistently. I wonder if this is a parallel case with Word 2007 not creating fully correct DOC files.