How to repair corrupt \windows\system32\config\system files?

T61 will not boot to Win XP - says the \windows\system32\config\system file is missing or corrupt.
BIOS hardware test of disk drive passes. When I place a Microsoft Win XP disk to attempt a repair, the message says there is no disk drive detected. I assume this is due to unique Lenovo HDD drivers that are not on the Microsoft disk.
Is there a way to repair this file(s) without doing a full HDD reformat?
THank you.

You need to include the Intel Matrix Storage manager via Floppy disk while running setup-CD or change in BIOS "Config"-SATA" to compatibility.
Then you can repair windows but first backup the hard drive onto annother disk f.ex with Acronis True Image Home (Emergency CD).
Boot from XP Retail-CD
`select "Install"
select the drive with the found windows installation and "Repir"
Windows Setup removes the system files and replaces them from CD
after systemreboot you willneed to re-install all patches and updates
My home-forum: http://www.thinkpad-forum.de
Wiki: Deutsches ThinkPad-Wiki English ThinkWiki
My ThinkPad-Collection

Similar Messages

Windows cannot start due to file is missing or corrupt Windows/system32/config/system

How do I recover system file from recovery disc ?

Hi,
You can get your missing file from an original windows installation disk.
To replace it you'll need a bootable CD or DVD to start your computer then put the file system (note that there is no extension) in Windows/system32/config/
Cheers,
Service is the lifeblood of any organization.
Everything flows from it and is nourished by it.
Customer Service is not a department... It's an attitude

Error message windows\system32\config\system does anyone know what to do to get it working again

Hi
This above errot message comes up when i try to booth up the computer, when bought the compyer did not come with disk butwas pre installed, its rather urgent as my dad's medical files are on there, any help will be appreciated

Hi silvanavandijk,
It would be very helpful if you post the whole error and not just the filename. Also it would be very useful to know what OS version/edition (for example: Windows Vista Prof x64) and thinkpad model you got.
I have seen errors that appear right when Windows start to load with a black screen that says windows\system32\config\system is missing or corrupt or something like that. Is that what you experience? I have also only seen this problem with computers running Windows Vista, are you using Vista?
If this is the problem you see the solution is to boot from a Windows DVD and choose the repair option instead of starting the windows installation. That should fix the problem. Another option would be if you got a image backup of the computer. Without the DVD i don't know how to fix this problem or if it's even possible.
-gan

Re: EQuium A100-147, wont start, \windows\system32\config\system -missing-

This laptop Equium A100-147started not connecting to internet normally, but would in safe mode.
So after trying virus scans-nothing.
System restore-nothing. I decided to put in the recovery disc and reinstall windows media.
I changed boot sequence to install it, changed boot sequence back to original.
It has reinstalled but will not go by the Windows Screen, A message has come up \windows\system32\config\system -missing or corrupt.
I cannot even see a way of doing a repair with this recovery disc??
Any help would be appreciated
thank you in advance.

That error means the Registry is corrupted.
The registry is made up from the following files:
c:\windows\system32\config\system
c:\windows\system32\config\software
c:\windows\system32\config\sam
c:\windows\system32\config\security
c:\windows\system32\config\default
You can restore these Registry files from the hidden System Restore folder on C: Drive.
Here are the instructions:
http://support.microsoft.com/kb/307545

How to repair corrupt MS Excel 2003 (XLS) File?

I have important MS Excel file data and unfortunately got corrupt due to virus attacks, so my crucial Excel sheet got lost, how to repair corrupt MS Excel 2003 (XLS) File? If have any solution please assist me.

A corrupt excel spreadsheet can be repaired by using Open and Repair technique. It is a built-in repair function that opens a corrupt excel file forcefully.
*Open MS Excel > press Ctrl+O > locate corrupt excel spreadsheet and select it.
*Click on the arrow shown beside Open button > select Open and Repair.
It will take just a few seconds to be completed and selected file will be opened, if possible.
Or if this doesn't work, one may take help of a third-party Excel Recovery software. I would recommend
Excel Repair Kit software to recover data from corrupt excel spreadsheet. The software is available with free demo version. To read more about this software and to download its free demo version, visit: http://www.excel.repair/

Foxfire downloaded an up-date last night (10 20/2010) at 5:30 PM EDST and it crashed the compter on re-start with an error message... Missing or Corrupt File ... WINNT\system32\config\SYSTEM

Foxfire downloaded an up-date last night (10/20/2010) at 5:30 PM EDST when I started Firefox, and it crashed the compter on re-start with an error message... Missing or Corrupt File ... WINNT\system32\config\SYSTEM. This machine is Windows 2000 Professional on Dell computer and Foxfire 3.6 or 4 not sure computer is stuck at the error message.

Hi there,
You're running an old version of Safari. Before troubleshooting, try updating it to the latest version: 6.0. You can do this by clicking the Apple logo in the top left, then clicking Software update.
You can also update to the latest version of OS X, 10.8 Mountain Lion, from the Mac App Store for $19.99, which will automatically install Safari 6 as well, but this isn't essential, only reccomended.
Thanks, let me know if the update helps,
Nathan

How to repair corrupted xp files with the Toshiba recovery dvd pkg

Hello all, my Satellite a105-s4054 has some corrupted xp os files. Please advise on how to repair only these files using the recovery dvd pks included with my sytem. I would rather not have to do a complete format and install. And it is now obvious which of the individual files listed should be replaced to repair the corrupted files.
Is there way to just replace the corrupted files?
Thank you

Satellite A105-S4054
..replace the corrupted files?
If they are system files, this will fix them.
Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe)
-Jerry

User profile in WINDOWS 8.1, 8, 7 redirected to C:\Windows\System32\config\systemprofile

Hi all,
When you are logging into Windows 8.1,8 or 7 using your user credential you will finaly end up as system service account or at least your profile will be recognized this way. This mean that system is now looking in C:\Windows\System32\config\systemprofile
for DESKTOP, DOCUMENTS etc.
I faced this probem few times on diffrent PCs. This problem has been out there for some time and peapole are tring to copy their profile to C:\Windows\System32\config\systemprofile. Sound no good for me.
Another way is to create new profile but it takes a lot of time and the problem sometimes comes back
http://windows.microsoft.com/en-us/windows/fix-corrupted-user-profile#1TC=windows-7
I manage to find out that the issue has something to do with the change of the registry at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-X-X-XX-XXXXXXXXXXXX
S-X-X-XX-XXXXXXXXX is your user SID. The to REG_DWORD that are changed
FLAGS
REFCOUNT
After you change values to FLAGS 1 and REFCOUNT 0 you have to log out. Now log in and you profile should be back again.
I hope that this will save you some time and that microsoft will finaly fix whatever cause this issue.

Hi Grzegorz,
Thanks for sharing and it will be very useful for the people who will come across the similar symptom in the future .
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

My Desktop went blank and an error message appeared saying C:\Windows\system32\config\systemprofile\Desktop refers to a location...

This the whole error message: C:\Windows\system32\config\systemprofile\Desktop refers to a location that
is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information
might h ave been moved to a different location
I restarted the pc and through the safe mode i copied the Desktop file that was missing at C:\Windows\system32\config\systemprofile\
from C:\Users\User. I restarted but i still get the blank desktop.
Can you guys help me out?

Thnx a lot LomM! My younger brother run the check disk and now it's working. But now im facing a different problem. With the sound drivers. I have not sound at all. And at Device manager I see yellow marked devices, giving me the code error 52 ("Windows
cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)").
So, I unistalled and re-installed but nothing. Still yellow marked. I did the Recovery thing (a couple of times using different dates ) but it did not complete successfully.
So I disable driver verification, while i was restarting my computer and now im getting the code 39("Windows cannot load the device driver for this hardware.
The driver may be corrupted or missing. (Code 39)").
it's that C:\Windows\System32\drivers\ktshunk.sys which is not getting verified. Any ideas?

C:\windows\system32\config\systemprofile\desktop was missing or could not be accessed

Dear All,
I am using Windows server 2008 R2. Last day the electric power was suddenly shutdown. When I reboot server, when I login with user administrator, my desktop don't appear, I found error:
C:\WINDOWS\SYSTEM32\CONFIG\SYSTEMPROFILE\DESKTOP WAS MISSING OR COULD NOT BE ACCESSED.
I try log in safe mode, it's also have same error.
I can't run any program. It's appear error that I don't have permission to access.
Could you help me to fix this error?

Check this URL : http://social.technet.microsoft.com/Forums/en-US/2eb4224d-3e8b-4705-8ed0-260012be2081/location-not-available-cwindowssystem32configsystemprofiledesktop-is-not-accessible-access?forum=winservergen
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Windows Deployment Service corrupts \systemroot\system32\config\software in images.

Hello,
Recently we have upgraded to Server 2012 R2 to handle our WDS services but some images are not deploying correctly.
When checking the event log on the machines that do not deploy correctly, the following error message is discovered: "\systemroot\system32\config\software was corrupted and it has been recovered'
We can restore the SOFTWARE registry backup from the regback folder and this corrects the problem, but this has to be done after the image is deployed and takes a lot of time.
The WIM files all deploy fine in all instances of deployment on Server 2008 R2, using DISM directly and ImageX.
For one image, this only occurs on certain machines. It has been tested on 3 Z200 with the same hardware setup and the error occurs on 2 consistently and does not occur on the 3rd.
On another one of the images, this error occurs every time it is deployed using Server 2012 R2 but never when deployed using WDS on Server 2008 R2, DISM or ImageX.
This occurs whether the deployment is set attended or unattended. The majority of deployments have been tested without using an unattended file to eleminate variables.
Does anyone have any suggestions? Any ideas would be appreciated.
Edit:
We have also exported the WIM file of the image that always "breaks" from WDS 2012 R2 and successfully deployed it every time using 2008R2 WDS DISM and ImageX.
We have created separate folders for these problem WIM files so that the RES file only contains the information from the specific WIM that is having problems; this does not fix the problem.
Edit 2:
There is an error in setupact.log but it onlys says that the mentioned registry setting is malformed or corrupt. I tried a web search on this and had results but the majority of the answers were related to errors sysprepping.
Starting WDS GUI
2014-02-12 16:47:07, Warning    [0x0a0180] UI     Failed to change the UI language to en-US.
2014-02-12 16:47:22, Error      [0x0a0052] UI     Failed to read image data from blackboard[gle=0x00000002]
2014-02-12 16:47:29, Warning    [0x07008d] DIAG   Win32_Processor : CoInitializeEx returned RPC_E_CHANGED_MODE. Continue. Error code = 0x80010106
2014-02-12 16:47:31, Warning    [0x070026] DIAG   Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0
Setting up disk
2014-02-12 16:47:51, Warning    [0x0606cc] IBS    DeleteFileEx: Unable to clear out attributes on [D:\$WINDOWS.~BT\Sources\Rollback\bootsec.dat]; GLE = 0x2
2014-02-12 16:47:51, Warning               WDS    CallBack_WdsClient_MulticastCopyFiles: Error transferring files. Falling back to unicast. Error [0x80070002]
2014-02-12 16:47:51, Warning    [0x0b0095] WDS    CallBack_WdsClient_MulticastCopyFiles: Multicast transfer failed. Error code [0x80070002].
Active Dir Setup
2014-02-12 17:11:21, Info       [0x0b0083] WDS    MgLibpOpenLdapConnectionFromDN: DN=
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
2014-02-12 17:11:21, Info       [0x0b007e] WDS    ProcessDomainJoinInformation: MachineName = [(null)], MachineDomain = [(null)]
2014-02-12 17:11:21, Warning    [0x0b0093] WDS    ProcessDomainJoinInformation: Error resetting machine account. Error [0x80070057].
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
Set up IBSLIB
2014-02-12 17:12:39, Info                  IBSLIB Copying files from D:\Windows\Boot\PCAT\en-US to \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US...
2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\bootmgr.exe.mui for read because the file or path does
not exist
2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\memtest.exe.mui for read because the file or
2014-02-12 17:12:39, Warning               IBSLIB Resource files missing from D:\Windows\Boot\Resources. These files are required for some editions of Windows. If you are servicing older
versions of Windows, you can ignore this message.
Sysprep Plug N Play
2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Removing the devices that are using service mpio ...
2014-02-12 17:14:54, Info                  SYSPRP SPPNP: The device Root\LEGACY_MPIO\0000 is using the service mpio.
2014-02-12 17:14:54, Warning               SYSPRP SPPNP: Error 0xE000020B occurred while adding device Root\LEGACY_MPIO\0000 to the device info set.
2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Finished removing the devices that are using service mpio.
Sysprep specalize
2014-02-12 17:18:11, Info       [0x0f008a] SYSPRP RunRegistryDlls:Retrieved section name for this phase as Specialize
2014-02-12 17:18:11, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Specialize
2014-02-12 17:18:11, Info                  IBS    Callback_Specialize: External Providers Specialized Succeeded
Modify boot entries (Non UFI)
2014-02-12 17:18:15, Info       [0x0606cc] IBS    Flushing registry to disk...
2014-02-12 17:18:17, Info       [0x0606cc] IBS    Flush took 1201 ms.
2014-02-12 17:18:17, Info       [0x06036b] IBS    Callback_SystemRestore: Successfully set System Restore state.
2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: There was an error getting the path to the boot.ini or ntldr. dwRetCode=[0x1F]
2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: We did not successfully complete ModifyBootEntriesLegacy. This is non-fatal, continuing setup. dwRetCode[0x1F]
Error in system log:
Log Name:      System
Source:        Microsoft-Windows-Kernel-General
Date:          2/12/2014 5:14:28 PM
Event ID:      5
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:
Description:
{Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-Kernel-General" Guid="{}" />
    <EventID>5</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-13T01:14:28.620907400Z" />
    <EventRecordID>12326</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="364" />
    <Channel>System</Channel>
    <Computer>COMPUTERNAME</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="FinalStatus">0x8000002a</Data>
    <Data Name="ExtraStringLength">36</Data>
    <Data Name="ExtraString">\SystemRoot\System32\Config\SOFTWARE</Data>
</EventData>
</Event>
Sysprep Panther Log:
2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Cleanup
2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Generalize
2014-02-12 14:40:10, Warning                      TapiSysPrep.dll:RetainTapiLocations:RegQueryValueEx() returned 2
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vhdmp was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service VMBusHID was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service Brserid was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbcir was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbccgp was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbhub was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service USBSTOR was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service sffdisk was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vpcbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service umbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service swenum was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service rdpbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service iScsiPrt was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service CompositeBus was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service circlass was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service ebdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service b06bdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service s3cap was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service 1394ohci was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbehci was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbohci was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbuhci was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ohci1394 was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HDAudBus was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrUsbMdm was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrSerWdm was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service MTConfig was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service mouhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service kbdhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sfloppy was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbprint was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidUsb was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service UmPass was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidIr was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBth was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BTHMODEM was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service hcw85cir was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WacomPen was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Processor was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service IPMIDRV was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service intelppm was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdK8 was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdPPM was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AcpiPmi was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service CmBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sermouse was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ErrDev was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WmiAcpi was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service flpydisk was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service fdc was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Parport was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service pcmcia was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service i8042prt was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.

We have discovered that this is only happening to target computers with installed
RAM greater than 4gb. If the machine has greater than 4gb of RAM, the mentioned corruption occurs. If the machine has
4gb or less, the corruption does not occur. We still have not found a fix for this, (besides removing the excess RAM during imaging and reinstalling after.) Any ideas/thoughts would be helpful! Thank you in advance.

Here's How to Repair your Windows Installation

Sometimes it is necessary or desirable to repair your Windows installation. For instance, you might see Windows showing unusual or unexplained slowdowns, failures to boot, devices no longer working like they used to, etc.
The following step by step procedure shows you how to do the repair. Note, that you will need the CD key that came with your Windows disk to complete this procedure.
1. Make sure boot order in BIOS is set to floppy (if you have one), cd/dvd, and then the HDD your original Windows was installed on.
2. Insert your original Windows CD into your cd/dvd drive (a slipstreamed cd with SP will also workif you have one). If the Windows Installion menu appears, select Install Windows.
3. If that menu does not appear, go to Start, Turn Off Computer, and then select Restart. After the POST, you will see a prompt, "Press any key to boot from cd..."
so press the space key (any other key will also work).
4. Let Windows setup continue.
5. After a short while you will see an option to repair your Windows using the Recovery Console. Do NOT select this option. Just continue.
6. Soon after this you will see a message "Searching for a previous Windows Installation".
7. When Setup finds your previous Windows installion you will be given an option to Repair that installation. Follow the prompt on the screen, i.e, press R to repair.
8. Now just let setup continue until it is complete and you see your desktop.
9. Then, go to Windows Update (Start, All Programs, Windows Update) and let it search for and install any available service packs, and/or other updates.
10. Lastly, if you have any drivers that are wish to use other than the ones in Windows, just install them in the normal fashion.
Now your Windows is repaired and fully updated, and hopefully the problems you saw previously have been fixed.

Quote from: Mike V on 30-January-07, 08:38:09
Thanks Bosskiller.
It seems everytime I do a fresh install I have trouble getting my cable internet going again.
I always seem to forget which files I need to download for the mobo to have access to that. ???
pickup drivers from here: http://www.msi.com.tw/program/support/driver/dvr/spt_dvr_detail.php?UID=436&kind=1
what OS you use?
"It seems everytime I do a fresh install I have trouble getting my cable internet going again."
where its connected via ethernet port or via USB port? if you connect it through on-board LAN you need to install chipset drivers 1st. if you connect it via USB port ensure your OS installation is with included SP2 on it if its XP. then install chipset drivers as well.
if you use 98 install USB 2.0 drivers 1st,(http://download.msi.com.tw/support/dvr_exe/mbd_dvr/USB2W9XME009.zip) before install cable modem.

How to reinstall my windows 7 operation system with out the dixk

How to reinstall my windows 7 operations system

You have to boot from the DVD. Put it in the optical drive, then shut down the laptop. Immediately after powering it on tap the Esc key. From the menu tap F9 Boot options. Use the arrow key to move down and highlight/select the CD/DVD drive, the tap Enter.
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

How to create a comment in config.ini file

Does anyone know how to create a comment line in the Essbase config.ini file (server config file, not client, if they are different)?I know that for ESSCMD it is :Calcs it is /*but not sure of syntax for commenting config files. Thanks in advance!

The comment character for the essbase.cfg file (I assume that is what you are talking about) is a semi-colon (;)Regards,Jade-----------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

How can I get back the default system files icons to my fles?

Hello,
After installing an application like FontExplorer, all my fonts got it's icon.
I went to a font, selected and did get info, I tried to delete the icon but could not.
I know the default icons for OTF fonts and an italic O, half green, half black.
How can I get those Icons back,
Or in general,
When files gets an application icons, how can I restore the default icons for files?
Thank you
Shlomit

Icons in the Get Info pane can be changed back to the original icon by clicking on the icon once, to highlight it, and then pressing Control X (for cut).
But in your case the font icon is probably more due to the association with the application selected to open it with, ie FontExplorer. So with the Get Info pane open for a selected font type you need to change which application you use to open it with. For example, if you select one of the OTF fonts and do a Get Info, in the Open With pane it will show FontExplorer. Change this to Font Book and it should change its default icon.

How to repair corrupt \windows\system32\config\system files?

Similar Messages

Maybe you are looking for