RegRepair Help File

RegRepair 2000
Version 4.0

Note: RegRepair 2000 should be used once a month or after installing new software or hardware and reinstalling Windows.

This help file answers every question we have been asked about the use of RegRepair in the last few years.

By Easy Desk Software


Getting Started
What is an IOS ERROR
Fixing IOS Errors
Fixing VXD Errors
Fixing VXD Errors for DOS
Compacting the Registry
Tech Support
Trouble Shooting RegRepair
Step By Step Instructions (for IOS)
Exception List
Compacting The Registry
What do the codes mean
Notes for Windows Millennium

Find IOS Error
Fix IOS Error
Fix VXD Error
Cabinet Files
Search for References
Other Utilities
Search and Extract files
Restore Bootup Settings
Backup Registry
Test Mode
Repair System File
Update System Backup Files
Registering Files
Duplicate Font Removal



If you are using the computer's manufacture's CD: During Fix IOS Error operation you may find that RegRepair 2000 cannot extract a file from the Cabinet files. You will need to use the Search and Extract feature. You must use the Setup feature on the main interface of RegRepair before attempting to repair the Registry.

Start RegRepair 2000 (RegRepair.exe) and click on Continue then click on Setup. When the Setup is complete you are now ready to use this program. After using the Setup feature you will need to create a current Bootlog. To do this you will need to click on the button Other Utilities and select bootup options and select show Boot menu, then Reboot your computer. You may also press the F8 key when you are reboot your computer to display the Boot menu instead of using the Other Utilities.

Back to Table of Contents

Getting Started

RegRepair 2000 repairs, restores, and changes entries in the Registry. It diagnoses and repairs IOS Errors. RegRepair's help file refers to RegMedic, RegMedic that is a separate program.

You should read the section about Cabinet Files to use this program correctly before attempting to use RegRepair.

RegRepair will only work on the machine that it is setup to. It cannot be used on a network drive. This program will not work with Windows NT, Windows 2000, or Windows 3.1. This program will not work on shared workstations. This program requires the Registry and Windows directory to be on the same computer as RegRepair 2000. Please read the Installation section on this page before using this program.

.In most cases reinstalling Windows does not repair IOS Errors. Windows simply adds information in the Registry so you are still left with a corrupted Registry after reinstalling Windows. RegRepair 2000 works best if it is installed and setup before you get a corrupted Registry. It works even if you install it after you have corrupted the Registry.

We have noticed that when you Fix IOS Errors on Windows Millennium, often Windows wants to restart in Safe Mode. We have found the by rebooting 2 or three times Windows will boot normally.

Back to Table of Contents

Find IOS Error

This button will start reading the Bootlog for failed files and then search the required directories to see if the file is present. If it is present it then checks for 0 byte size files and then RegRepair codes a report that it displays in the current window. You will need to create a new Bootlog each time you use the Find IOS Error function. This will insure that no entry in the Registry is being removed or changed incorrectly.

To create a Bootlog you will need to make sure that the function keys are enabled. Use RegRepair and select "Other Utilities" then select "Restore Bootup Setting" and check the box "Enable Function Keys" along with any other options you wish. Reboot and when you see the "Starting Window" immediately press the F8 button, then select "2) Log Boot /Bootlog".

Back To Top

Fix IOS Error

This button becomes activated only after a search and the Find IOS Error button has made a report. RegRepair 2000 then searches all directories again and then checks if they are standard Windows files or installed by other programs. RegRepair 2000 will then either replace the corrupted file or fixes the Registry. If it is not a standard Windows file for your version and it is present, RegRepair 2000 will ask you if you want to delete the file. RegRepair 2000 will make a backup of the Registry and the file, than deletes the references to the file in the bootup Load File Sections. When RegRepair 2000 has finished with the Failed Load files you will get a report in the current window. You will also have a file written in the current directory that is called Report.txt (to review later). RegRepair 2000 will also create a list of files that you should search for manually. You will find this list when you click on the Search for References button. Before using the Search for References button use the Other Utilities Button first and use the Search and Extract Button.

In all cases you will need to reboot and create a new Bootlog to verify that files have been repaired. You may need to rerun the FIX IOS a third time. RegRepair 2000 will search the each time differently for a proper repair of the failed file. If after the third attempt RegRepair has not repaired the error. Read the report and follow the steps that RegRepair recommended. Also view the Exception List.

Be sure you make a backup of the Registry EACH TIME you use this function. Place in a folder you can get to.

Back To Top

Exception List

This is a list of files that RegRepair may not be able to fix because the file is unknown, not present on your system, or no entry in any of the system files was found. If you find a file not on this list you may check our site at for newly added files. If RegRepair finds a file with no name it cannot fix it because the file is unknown.


SDVXD This file is an alias; the real name of the file is unknown at this time. This file will not cause an IOS error. Windows 95/98 automatically loads a miniature disk cache to increase the speed of the boot process. When the boot process is complete, the miniature disk cache is unloaded from memory. When it is unloaded, the above line is added to the Bootlog.txt file to indicate that the miniature disk cache has been removed from memory. This is normal behavior, if you have OSR2 (Windows 95 B) or a newer version of Windows and this error is not present then you have other problems. Look for hardware problems during bootup.

VEPSD This file is an alias; the real name of the file is unknown at this time. It is the Virtual Extended Paging Services for Borland C++

EBIOS The extended BIOS driver did not find extended BIOS, so it does not load.

NDIS2SUP.VXD The NDIS 2 support driver did not find any NDIS 2 drivers to support, so it does not load.

NTKERN.VXD This file is for OSR2 update for USB support available, download from Microsoft

NAAPI.VXD This is Creative labs driver and was designed for the Japanese version of Windows. The sound card is attempting to load this file so you receive an error message if you are not using the Japanese version of Windows. Windows has already load another driver for you sound card.

NAVENG.VXD It is normal for this bootlog failure to occur. The ability is built into
Norton Anti virus to have it use a NAVENG.VXD file which (if necessary) could be
included in the set of virus definition update files and quickly distributed to Norton Anti Virus users and immediately put into use by their systems without need of a special patch or anything else being done. There is, however, currently no need for the NAVENG.VXD file, hence no NAVENG.VXD.

Nuwave.drv This file appears to be loaded via the sound card in some case and through the Media key in other cases. The file is not available so Windows use a substitute driver. See you sound card manufacture.

MTRR.VXD This file required for DirectX5, download from Microsoft or reinstall DirectX5

VPOWERD The Advanced Power Management (APM) driver determined that your computer does not support APM, so it does not load, or APM support may be disabled. To determine if you have inadvertently disabled APM in Device Manager, follow these steps:

  1. In Control Panel, double-click System.
  2. Click the Device Manager tab.
  3. Double-click the System Devices branch to expand it.
  4. Double-click the Advanced Power Management Support branch. (If this branch does not exist, your computer does not support APM.)
  5. Click the Settings tab.
  6. Verify that the Enable Power Management Support check box is selected.

Vserver.vxd Vserver.vxd does not load statically so that it can save memory by loading later in the boot process only if it is needed. For example, Vserver.vxd might not be needed when you start a laptop computer while it is out of its docking station.

VSHARE If you examine the Bootlog.txt file, you will notice that VSHARE loaded successfully earlier in the boot process. The second copy of VSHARE detects that VSHARE is already loaded and does not load.

JAVASUP The Java Support driver is not needed on your computer, so it did not load. Java is a programming language used on the World Wide Web (WWW). Microsoft Internet Explorer versions 3.0 and later include a Java subsystem.

Back To Top

Cabinet Files

RegRepair is designed to use Microsoft's Windows Cabinet files. Cabinet files are the files that you use to install Windows. They have names like or

If you use the computer manufacture's Cabinet files that are on your restore CD RegRepair may not be able to locate the replacement files in the corresponding Cabinet file. Because the manufacture has rearranged the cabinet files to suit their needs. You should use the Companion CD that came with your computer. If you do not have this then you may have to use the search and extract feature during repairs. RegRepair will create a library using whichever cabs you direct it to, and attempt to locate the file using this library first.

It is advised that you copy all the Windows installation files you your hard drive. The reason is two fold, one - in the event you ever need to reinstall Windows and cannot load your CD-ROM driver, it is also faster to install. Two - many of the Windows 98 CDs have and an invalid content table which causes software to be unable find files.

As a special note: Files not found in the cabinet files may have been renamed by Windows after they have been extracted. Files that are not in the Windows Cabinet and have not been renamed after extraction are installed by other hardware that you supplied the disks for. Before removing entries in the Registry for these files. Make a backup of the Registry.

Back To Top

Search for References

This button will bring up a new window. This window will search for the original Setuplog file that was written the day you last installed Windows. If you have not deleted this file RegRepair 2000 will verify if Windows installed the file in question. If there are no files that you need to search for you will get a message "no files to search for". If there are any files that your need to search for, the file name will be in the lower text box of this window.

To use this feature click on one of the options and then click the Open File button. Use the Find feature available in each programs Menu Bar Item. The Registry Editor's "find" feature will be found under the Edit Menu, while the other files find feature will be found under the Search Menu.

Type the file name in the Find window and then remove all references each file.. If you wish, you may place a semi colon in front of the line instead of deleting the reference in all file except the Registry. However, in the Registry you must delete the reference, therefore you may wish to make a backup first of the Registry if you have not already done so. Use the Other Utilities button to make a backup.

After you have searched all files, click on the Next Search button to bring up the next file to search for. When you have finished searching for all files the message "No more files to search for" will appear. Simply click on the finished button to close this window.

Back To Top

Other Utilities

This button will access a new window with several other utilities. The Search and Extract files, Restore Bootup Settings, Install Backup Registry, Reset Registry Setup, Backup RegistryRead Bootlog, and Repair Icons which restores miss matched Icons. The Check Libraries button is used to verify if RegRepair knows a file or if a file is available in the Cabinet files. To change the browser used for viewing this Help file click on Select New Browser.

Back To Top

Step By Step

To check for, or repair a IOS Error: You need a current Bootlog, you can create one by rebooting and when you see the words Starting Windows 95, 98 click on the F8 button and select Log Boot. You may also have RegRepair display the Boot Menu, using Other Utilities and Restore Bootup Setting. If you have problems getting the Boot Menu to Display, make sure you have enabled "Use Function Keys".

Open RegRepair 2000 and click on find IOS ERROR. When RegRepair 2000 displays a report in the window and a message at the top of the interface the Find part is done.

Next click on Fix IOS Error. When this part is done a new report will be created. If you exit this window the report text can be viewed in Notepad. The report is a file in the RegRepair 2000 directory named Report.txt. This Report is created as RegRepair is checking files and entries in the Registry. You may find that one line that says for you to delete an entry and a line or two later it says entry found and deleted. This means that during the first part of RegRepair's search no erroneous entries where found, then RegRepair found entries during the second part of the search that are duplicate loading instructions for Windows and made the repairs.

Generally if RegRepair asks you a question it is recommend that this operation should be done. The message boxes are used to keep you informed and allow user intervention to adjust the results.

To search for references click on Search for References. Also read Fix IOS Error. If the file is missing you will get a code 5 or 10, then you will get a printed statement that the file is missing. This means that the file is not in the required directory or in Windows Directory and sub Directories.  If you only get the code 5 or code 10 the file may be in another directory. Read the report carefully. If you get, code 002, 5, or 10 then the file is missing or in the wrong directory. If the file is missing it is recommend that all references be removed, you can always register it again correctly if you find it on your system somewhere else later.

If the file has a fail code of 5, 10, or 002 then you should remove all entries in the Registry and other system files. If it has any other fail code then remove all entries form the System.ini, Win.ini, Autoexec.bat, and Config.sys. Then create a new boot log and check to see if the fail file has been repaired. If not, you will need to edit the Registry manually looking for more entries. Remember RegRepair will look at files differently after it has replaced them once. So you may need to run RegRepair two to three time to fix some problems. To run RegRepair again you must use a new boot log each time.

Never remove any entry in the Registry under the key Vmm32Files. When editing the Registry, make a backup first remove the attributes to both the Registry files and the backup files while in Windows. Then remove one or two entries and reboot. If you have a problem replace the Registry from DOS, if you're in Windows RegRepair can replace the Registry for you.

Be sure that you Reboot and create a new Bootlog after fixing IOS errors. Then use the Other Utilities button to read and search the Bootlog.

If you get locked out of Windows because of on IOS error: go to the DOS prompt and then to the Windows directory and TYPE the word WIN. This may get you in Windows.

Back To Top


TTF file: To register a font file, you can open the Explorer and copy the file to the Font folder in the Windows' directory. You can un-registered a font by deleting it in the Explorer.

DLL files: To register a DLL file, right click on it and select Open With the file Regsvr32.exe. It should be found in the System Folder.

VXD files: Copy the file to the folder system\Iosubsys.

Back To Top

Fixing VXD Errors

The VXD utility should not be played with just to see what it does. It should be used only when you need to stop VXDs from loading or when you have a Windows Protection error or Blue Screen of Death constantly.

There are three parts to the Fix VXD feature. The DOS version, the Display VXDs, and the Fix Windows Protection Error.Please remember that if you stop a VXD that Windows must load in order to reboot you will not be able to reboot to Windows. Make sure you know how to undo changes before using this utility, by using the C:\Undovxd.bat file and/or restoring the Registry. See Backup Registry. If the VXD was stopped and the file resides in the Windows\System\Vmm32 folder or the Iosubsys folder the files have been renamed to the sav extension. The Undovxd.bat file will rename the file back to the vxd extension.

Display VXDs

Use this feature when you get the Blue Screen of Death stating that an invalid call from module ????.VXD . Click on the Display VXDs then the two windows will fill up with vxd file names. Select the file you want to stop from loading. Select only one file and reboot. When selecting a second file do not tell RegRepair to replace the backup information. If for some reason you do backup the information a second time and later find you need to undo any of the Fix VXD functions a complete backup is available in the sub folder "Sysbackup" of RegRepair. Each time you select to stop or start a VXD the undo files are overwritten so be sure to select only one file and reboot.

Fix Windows Protection Error

Use this feature ONLY when you boot to Windows and you get the Blue Screen of Death stating that an invalid call from module ????.VXD has caused and error; AND you are unable to make the needed repairs using the Display VXDs feature. Using this feature will remove all VXDs from loading except the bare minimum. You will need to reset your display adapter and other hardware as well as any software that loads on bootup with a driver (VXD). Use this feature when you can only enter Windows in Safe mode. Using this feature should save you from having to format and losing all your software setting in the Registry. It should be able to fix VXD errors that even reinstall Windows does not. Unfortunately we cannot say it will always fix all VXD errors causing the Blue Screen of Death due to the fact that you may have a corrupted VMM32.vxd file. RegRepair cannot built a new Vmm32.vxd file. How ever, you may visit our site and read the page "How to repair the VMM32.vxd file". Using this feature will require you to reboot and Windows will reinstall your hardware and many of the VXD files Windows requires. Backups will be made and kept in the sub folder "Backup" of RegRepair. You can access them from DOS. There is also a txt file created in the Backup folder that you should read before using these backups. If you are unable to enter Windows even in safe mode you should use the DOS version.

Fix VXD Error from DOS

For registered users only

RegRepair 2000 has place a bat file in the root directory ( C:\ ) named FIXVXD.bat These file will have the same effect as the Fix Windows Protection Error in RegRepair. These function should ONLY be used when you ca no longer get into Windows in Safe Mode.

Reboot and hold the Control "CTRL" key down while boot up. Start holding the key down after your mouse and Keyboard is loaded. This will have the same effect as pressing the F8 button. When the boot menu is displayed select Command Prompt and at the C: prompt type FIXVXD and you will be prompted the rest of the way

Back To Top


1 .... 2 3 45 .... 6 .... 7 .... 89 10

20 ..... 21 .... 2223 24 .... 25262728


002 003 0016

When reading codes remember that the report is done in steps
This means that during the Find or Fix IOS Error operations you get a code number on the second line; then later in the report RegRepair 2000 will tell you it found the file. The codes 1 - 10 are the codes generated when RegRepair 2000 was Finding IOS Errors. Code 002 - 0016 are Windows' codes and codes 20 and up are generated while RegRepair 2000 is fixing the errors.


Code 1: This is a file with a path and is present on your computer. It is probably corrupted. This may not be a standard Windows file. Try the Search and Extract feature and install a new file. The file may also have an incorrect path

Code 2: This is a Virtual Device Driver (.vxd) file and is present in the System directory. It did not load and may be corrupted or another program is trying to manage memory causing this error or Windows was able to initiate it during bootup. Try reinstalling this file. If this problem continues read What Else Can I Do

Code 3: This is a memory or Port file (.386) and is present in the Windows or System directory. It did not load and may be corrupted or another program is trying to manage memory causing this error. Try reinstalling this file. Most of the 386 files are for DOS and may not be needed on your system if you don't use DOS programs. 386 file are also used for communication ports, check the Device Manger for conflicts. Check all the DOS programs you have installed using this driver and reinstall it if it is not a standard Windows driver.

Code 4: This is not a file. This means that the Registry is corrupted or that the IOS errors have caused this problem. Fix all the IOS errors and reboot. This may fix this problem. If you have no IOS errors then the Registry is corrupted and you should try using the Repair Registry button to access RegRepair Plus (if it is installed on you machine)

Code 5: This file is missing. The file has no extension and is unknown to Windows at this point in the report. Try read the file Cab.lib in the RegRepair folder and locate a file that has the same name to obtain the file extension then use the Search and Extract feature, this may be a standard Windows file. This file probably has been added by another program. You may have to reinstall the program or remove all references to this file. Use the Search for References feature. Also see the Exception list.

Code 6: This file is a font file that did not load, it is present and probably corrupted. Try reinstalling it. If RegRepair 2000 is unsuccessful try manually reinstalling it. If the file is corrupted Windows will tell you and then be sure to use the Search for References and delete it's reference from the Registry.

Code 7: This file is in the Windows directory. It may be corrupted or Windows could not load it at this time. Try reinstalling this file. This file is probably not a standard Windows file and was added by another program. Also read What Else Can I Do


Code 8: This file is present in the System directory. It may be corrupted or Windows could not load it at this time. Try reinstalling this file. This file is probably not a standard Windows file and was added by another program. Also read What Else Can I Do

Code 9: This is a driver file (. drv) and is present. It may (probably is) be corrupted or Windows could not load it at this time. Try operating all hardware to see what program has added this file. You will find a problem with that piece of hardware if it is a hardware driver. Also read What Else Can I Do

Code 10: This file is missing. The file is unknown to Windows at this point in the report. Try using the Search and Extract feature, as it may be a Windows file.

Code 002: This code means that this file is missing (or not present in the required location). This file will need to be replaced or all references removed from the System.ini and the Registry.

Code 003: Windows usually gives this code to a file that is not in the Windows directory (not required by Windows) that is missing or corrupted.

Code 0016: This code means that the file is corrupted and will not be loaded. If it is a font file sometimes just making a copy of the file then deleting it and then reinstalling it will fix the problem. Replacing this file is suggested.

Code 20: This code means that the cabinet files that you are using are not those from Microsoft; these cabinet files have been altered by your computer manufacture. Or you are using a foreign version or you have selected the incorrect version of Windows in setup. You will probably have to use the search and extract feature on most files.

Code 21: Windows calls this file and yet it is not available on any version of Windows. No references have been found to this file in any section of the Registry that Windows uses to boot. This error will cause you to get locked out of Windows on is' own. RegRepair 2000 will still attempt to search the Registry to remove references to this file  If you do find a reference to it, remove it and please notify us at  of where you found the reference.

Code 22: This is a common file and line to fail. If no other line appears about this file failing then this is not a problem. RegRepair 2000 will still attempt to make repairs in case this file is corrupted or trying to load twice. Also read
What Else Can I Do

Code 23: Your ISP (Internet Service Provider) and Dial Up networks use this file. It is available in the cabinet files. Windows does not always load this file successfully but it usually does initiate it during booting. This file is probably being loaded several times. Also read What Else Can I Do

Code 25: This file should not be used with Windows. Windows uses Vcache and this file interferes with Vcache. It is recommended that you remove all references of it for the system files. This file should only be loaded when and if you are running DOS programs. It is recommended that you use 2 autoexec.bat and 2 Config.sys files to fix this failure.

Code 26: The cabinet file may be corrupted, does not exist, or you stopped the extraction. If the cabinet file is corrupted you will need to obtain a new one. If this file is not installed as part of your Windows cabinet file you will need to reinstall the associated program or delete the file and all references to the file

Code 27: This if is an alias you will need to search all system files for the alias name. The alias name may not be found.  At this writing no alias files that fail in the bootlog are known to cause a problem in operating Windows. See Exception List

Code 28: Reboot and create a new boot log, if the file still fails then do a manually search of the System.ini, Config.sys, and Registry, remove all references to the file except from the Vmm32File key.

Code 30: See Exception List

Code 31: RegRepair will not install fonts, this is because the font was install without Windows verification the first time, allowing installation of a corrupted font. If you install the file manually Windows will not allow you to install it if it is already corrupted in the cabinet files. Be sure to do a search using Find Files or Folders for any font that RegRepair cannot delete. A list will be available in the Search.txt file, use the button Search for References to access this file.

Back To Top

Search and Extract files

To access this feature you will need to click on the Other Utilities button of the main interface. Then click on the Search and Extract button.

This feature will allow you to search and extract a file from the Windows cabinet files, the files used to install Windows. This window is self-explanatory. Just fill in the center window with the correct spelling and extension of the file you wish to extract. Make show the correct location of your cabinet files is displayed in the top window. The lower window is for the location you wish the file to be extracted to. You may also change the location of the directory you wish to place the file in (the lower window).

Back To Top

Restore Bootup Settings

To access this feature you will need to click on the Other Utilities button of the main interface.

This feature will reset the bootup information such as splash screen settings, delay time, autoscan, etc. Be sure that you always have the Enable Function Key checked.

Back To Top


This is the most important feature of RegRepair 2000. DO NOT attempt to make any repair with RegRepair until you have used this button. This operation will go through the Registry and read all settings that are needed fix IOS errors. You must verify or correct this information before attempting to use RegRepair 2000. To update your information to RegRepair 2000 at a later date click on Setup again. You need only use the setup button once unless you update or change your version of Windows.

Back To Top

Test Mode

This feature allows you to try RegRepair 2000 without making any changes to the Registry. You will be able to see what Keys would be altered, and it will still tell you what is wrong in the Registry. However it will move files but it will not replace files.

If you click on this button a second time you can disable test mode. When you exit RegRepair Test mode is disabled.

Back To Top

Backup Registry

To access this feature you will need to click on the Other Utilities button of the main interface.

This feature makes a copy of the Registry at any time. RegRepair 2000 will name the backup files with the .000 extension in the Windows folder so not to be confused with the Windows or ERU's backup files. No attributes will be placed on these files. This makes it easy for users who are not familiar with hidden system files to copy these files from DOS.

There is a second backup copy that RegRepair created the very first time you started RegRepair.
It is in the RegRepair sub folder Sysbckup. They are stored with the dat file extension. To update these files and the Reg files stored here delete the file Regrep.sfc in the RegRepair folder and the file C:\Fixvxd.bat and then start RegRepair. Reg files are also stored here. To install a Reg file copy the file to Windows or your desktop and double click on it. To install the Reg file from DOS - at the Windows prompt type: RegEdit Name_of_File.reg and press enter.

DOS is available on all Windows 9x and Millennium. For Windows Millennium use a startup disk and boot to an A: prompt. then type:
C: and press enter
CD\Windows and press enter
You will now have access to the DOS commands from the Windows\Command folder.

To restore the Registry from DOS using these backup files type at the windows directory:
Attrib -H -R -S System.dat
Attrib -H -R -S User.dat
Copy System.001 System.dat
Copy User.001 User.dat

Windows Millennium also has a file "Classes.001" and Classes.dat

If you compact the backup files have the extension sav instead of 001 so that they do not get overwritten.

Back To Top

Repair System Files

This feature checks to see if a setup program has replaced any of Windows system files with older files and then after prompting, RegRepair 2000 replaces them if they have been changed.

Back To Top

Update System Backup Files

This feature checks to see if the Windows system files are newer then the backup files in the Sysbckup folder, after prompting, RegRepair 2000 replaces the backup files with the newer version.

Back To Top

What Else Can I Do

First thing  you should do to verify a problem is Reboot and relog a new Bootlog. Then read it using the Read Bootlog button. See Other Utilities. Allow RegRepair 2000 to search for you the first time. Pay close attention to the message boxes. Remember that in this mode RegRepair 2000 will read and display all lines containing this file. Each file action is represented in the bootlog as: the first line is the action taken, the second line is the success or failure line.

If the file fails to load but does initiate successfully then the problem is that Windows could not load it completely into memory at load time because the previous file was not done loading, or the file required another file to be loaded first..

If the file fails to initiate but does load then you have a conflict with memory managers or a vxd file. Check to see which files are also failing.

If the file fails to load and fails to initiate then the file is probably corrupted and if you have reinstalled and still have this problem then the source file is corrupted. You will find this most commonly with font files.

SYSCRINICOMPLETEFAILED usually means a problem does exist. Search for the file on all drives and in all files. Try and verify if it is corrupted or missing.

The information in BOOTLOG.TXT is written in sequence during startup, in roughly five major sections. Depending upon a specific error condition, you might need to examine multiple sections. Notice, however, that a loadfailed= entry means only that the related VxD refused to load. For example, loadfailed=ebios indicates that the EBIOS driver did not detect EBIOS in the computer and so reported that it should not be loaded. The following table shows the sections to examine, and describes the possible errors and methods for correcting those errors.

BOOTLOG.TXT Sections for Determining Errors

Section and errors    Corrective action
Loading real-mode drivers:   
No XMS memory    Verify that the section contains this entry:loadsuccess=c:\windows\himem.sys If not, verify the file and entry in CONFIG.SYS
Incorrect MS-DOS version (message appears when driver loads)     If this error appears when loading drivers or programs that worked before, verify that the section contains this entry:loadsuccess=c:\windows\setver.exe.
Windows doesn’t start on a SCSI hard drive    Verify that the section contains this entry:loadsuccess=c:\windows\dblbuff.sys
IFSHLP.SYS message occurs    Verify that the section contains this entry:loadsuccess=c:\windows\ifshlp.sys
Loading VxDs:   
Verify the loading, system, and device initialization of all VxDs by checking the section for these entries:loading vxd = ios
loadsuccess = ios
Cannot access D??SPACE drives    Verify that the section contains this entry:loadsuccess = c:\dblspace.bin
Sharing violations occur    Might be due to failure of the Vshare VxD to load. The section might contain an entry such as:loadfailed = vshare
System-critical initialization of VxDs:   
System-critical initialization error occurs    Verify that this section contains entries such as:syscritinit=ios
Device initialization of VxDs:   
Verify that the section contains entries such as:deviceinit=ios
Successful VxD initialization:   
Verify that the section contains entries such as:initcomplete=ios
The following table shows the kinds of entries in BOOTLOG.TXT to examine for information about the system startup process.

BOOTLOG.TXT entry    Description
Error    Errors that were logged during startup
Fail    Failures that occurred during startup
Dynamic load success    Dynamically loaded VxDs
InitCompleteSuccess    Loaded VxDs
LoadStart, LoadSuccess,
Loading Device,
Loading Vxd    Indication of loading processes
LoadFailed    Indication that component failed to load
SysCritInitSuccess    System initialization actions
DeviceInitSuccess    Device initialization actions
Dynamic load device, Dynamic init device    Dynamic loading and initialization of devices
Initing, Init Success, InitComplete, Init,
InitDone    Initialization actions
Status    Current status indicator
For example, if you see an entry such as DynamicInitDevice=PPPMAC but there is no matching entry such as DynamicInitSuccess=PPPMAC, then that VxD failed to load. If a driver in the Windows SYSTEM\IOSUBSYS directory stalls when it is being initialized, you can sometimes successfully start the system by renaming that file.
The following shows a sample BOOTLOG.TXT file:

Loading Device = C:\WINDOWS\HIMEM.SYS
Loading Device = C:\WINDOWS\EMM386.EXE
LoadSuccess = C:\WINDOWS\EMM386.EXE
Loading Device = C:\WINDOWS\SETVER.EXE
Loading Device = C:\WINDOWS\IFSHLP.SYS
Loading Vxd = VMM
LoadSuccess = VMM
Loading Vxd = nwlink.vxd
LoadSuccess = nwlink.vxd

Loading Vxd = vnetsup.vxd
LoadSuccess = vnetsup.vxd

Back To Top

Read Bootlog

If you use this feature RegRepair 2000 will ask you if you want RegRepair 2000 to search for a file.  If you choose Yes then a small window will appear and you can entire a file name and RegRepair 2000 will show you every line in the Bootlog that contains this line. Enter the file name without an extension and then search. You may do a second search with the file extension.

If you would like to read the Bootlog yourself then when RegRepair 2000 prompts you select NO.

Back To Top

Duplicate Font Removal

This utility will check the font folder for files that are hidden to your view because they are not installed, checks for font that are no longer installed or incorrectly installed. Then installs or removes them. If a font file cannot be verified the utility will copy the file to a sub folder named Installfont. You should have Windows in stall these font files. You may find that the file is already installed. This is because the file name in not in the library and the font name is not in memory. The files in the Installfont folder are placed there for you to verify, they have not been removed from the font folder. Files placed in the C:\SavedFonts folder are duplicate fonts that are not needed or file that have been incorrectly placed in the font folder.

After using this utility you should create a new boot log and use the Find IOS Error utility.

Back To Top

Once you have clicked on Continue, the program opens to a screen that will allow you to find and repair IOS errors. If you do not know what an IOS error is..... When Windows is booting up you see the screen OS Loading and Starting Windows 95. After this may come messages that tell you that a file cannot be found or if the file is critical you will get a message IOS ERROR and the boot up will take you to the c:\ prompt instead of Windows.

You probably have IOS errors right now and Windows just steps over them, not even bothering to tell you about them until it is too late. If you have enough small errors Windows will not boot. Font files are the biggest offenders. Note that Windows may report them as corrupted and they may not be at all. To fix this you MUST let RegRepair remove them, then fix all the other IOS errors. Now reboot and have Windows install the Fonts in the backup folder. Many times you will find 20 to 300 Fonts listed as code 0016. Odds are it is another problem that is causing Windows not to be able to load them. See Fixing IOS Errors

Back to Table of Contents

Compacting the Registry

Read this entire section before Cleaning and Compacting the Registry. Be sure to make a current backup of the Registry before compacting. You should also make a startup disk if you do not already have a current one. It is recommended that this section be printed out! If you have Windows ME please see

You should also check your memory, you will need to have a minimum of 569,000 bytes in DOS. If you use buffer, stacks, or files in the Config.sys, rename the Config.sys before rebooting. This will increase you available memory. If you do not have enough available memory in DOS then this process will stop before it is completed.

This feature should not be used if the Registry is corrupted as the operation is highly likely to fail during the Compacting stage. If RegRepair tells you that the Registry is corrupted while attempting to Clean and Compact the Registry - visit our site and read the page "How to repair the Registry". You MUST use Scandisk before Compacting. If you do not you may have an error on your hard and your system will hang up during the building (Cleaning and Compacting) of the new Registry. If this happens, reboot and try a second time. Your machine may (in rare cases) not continue to boot to Windows after finishing Compacting and may reboot and try to Clean and Compact over again. If the second time hangs then reboot and press the F8 key to display the bootup menu and select command prompt only from the bootup menu. Then at the C prompt type the word Clean and reboot. If you are unable to get to the Boot menu use your startup disk to reboot your computer to the A prompt than type:
C: (press enter)
Clean (press enter)

If you need to replace the Registry continue:
cd\windows (press enter)
Attrib -h -r -s System.dat (press enter)
Attrib -h -r -s User.dat (press enter)
copy System.sav System.dat (press enter)
copy User.sav User.dat (press enter)
Press Ctl-Alt-Del to reboot

If your Registry is corrupted (you get an error in the bootlog or a notice on bootup to Windows) the Compacting process will stop. If you system hangs during the compacting stage you have a disk power saver on, check the Bios. If the process fails to complete the registry is too large. If you have Windows 95 no letter or A you will need to update your RegEdit file with a newer version from Windows 98 or Windows 95 B

The entire process on cleaning and rebuilding the Registry can take as long as one hour for a small Registry and 3 for a large Registry. This process may be less depending on the condition of your Registry and the speed of your computer. During this process you will view a percentage of completion, at times this percentage will move rapidly and at other times it may stay at a percentage (example 57%) for about five minutes. You will be able to tell if your system hangs by view the hard drive active light on your computer or if a percentage stays longer than 10 - 15 minutes.

If you do have the file Smartdrv.exe installed to the Windows folder the process will be much quicker.

Should a problem occur there is a backup of the Registry named System.sav and User.sav in the Windows Folder, and you may also find backups with the file extension 001 and da0 ( d a and zero). The da0 extension will have the h r s attributes, you will not need to remove the attributes (Attrib command) and there is also a Backup of the Autoexec.bat file in the root directory named C:\Autoexec.wos.

You will find a second backup copy of the Registry in the sub folder of C:\Progra~1\Easyde~1\RegRep~1\Sysbac~1 and the files are named System.dat and User.dat. You will not need to remove attributes from these file either.

If you elect to use Compact with minimal information a new Registry will be constructed with just the required Keys for rebooting when you compact. You can then import the complete Registry once you are back in Windows by double clicking on the file Complete.reg on your desktop.

If you elect to compact using original Registry you may need to reinstall some of your software and hardware, depending on how long ago the it was since you last installed Windows. This option should be your last resort.

If you compact using Compact with minimal information or original it is suggested that you disable the Registry Scanner on Window 98. You can do this by renaming the files C:\Windows\Scanregw.exe and C:\Windows\Command\Scanreg.exe. Once you have rebooted a few times you can rename them back.

You will also find more information at Trouble Shooting below

Back to Table of Contents

Trouble Shooting RegRepair

Boot Menu still shows
Cannot find cabinet files:
Compacting the Registry Fails:
Compacting the Registry on every reboot:
Computer Lockup during Repairs
Duplicate Fonts Problems:
Failed Files Not Fixed:
Files have been deleted that you need:
RegRepair cannot Shut down Windows:
RegRepair Runs Very Slow or the Mouse Moves Rough
Verifying Cabinet files hangs or you replace Extract.exe or Reinstall Windows:
Video becomes corrupted

Boot Menu still shows: If during the bootup of Windows you still get the boot Menu showing, use the button "Other Utilities" and the use the button "Restore Bootup Setting" on the Window that opens. Uncheck the box "Show Boot Menu".

Cannot find cabinet files: If during the setup (using the setup button) RegRepair cannot find you cabinet files then you can do one of two things. First try copying all files in the Win95 or Win98 directory from your CD to a new directory named Windows\Options\Cabs and then rerun the RegRepair Setup command. The path must be in 8.3 format for RegRepair to get the information that is needed. Or verify that the cabinet file that RegRepair is looking for exists. If it does not create it by copying another cabinet file to the new one. Example: Copy to, you are missing this file. This is not a fix for the missing file, simply a walk around. If you are using a Windows 98 CD, you may need the Win98 folder to your hard drive, we have found many CDs invalid FAT.

If you still have problems enter the words "cannot find" in the window that displays the cabinet file path\name. RegRepair will build a new library without verifying the cabinet files. You must be sure that the cabinet files exist in the location that you entered earlier. If you have WIN98 your CD may be corrupted. We have notice that many of the upgrade CDs appear to have been made with a bad FAT on the master.

Compacting the Registry Fails: This means that the Registry is corrupted and cannot be rebuilt. The best way to fix this is to try defrag and scandisk, reboot several times until Windows can shut down quickly and then reboot. Then try opening all your software and using each one. This process can help rewrite damaged keys. Then try compacting the Registry again.

If the above procedure does not work then visit our site and read the page "How to repair the Registry".

If your Registry to over 10 Megs it may also fail because the Registry is too large. If you have Windows 95 A version it may also fail because RegEdit cannot import a large text file, try obtaining new version of RegEdit

Compacting the Registry on every reboot: This means that Windows messed up (hard to believe). RegRepair made an entry in the Autoexec.bat file and gave Windows the instructions to start C:\Clean.bat and replace the Autoexec.bat with Autoexec.wos and Windows did not. You can remove all the lines from the Autoexec.bat file starting with @echo off, Compacting Registry to the bottom of the Autoexec.bat or you may replace the file with the file Autoexec.wos. Windows was instructed to replace the Autoexec.bat and also instructed to start RegRepair 2000 on reboot to check that this was done; but the entries in the Registry may have been removed. See Compact and Cleaning the Registry. Note: Windows was instructed to replace the Autoexec.bat file. and to start Clean.bat, and to start RegRepair on bootup to triple check that all files where cleaned up. But Windows does mess up!

Duplicate Fonts Problems: You may find that after using this feature you get the same messages, Reboot and try again. If after two times of rebooting and using this utility the same files are coped to the SavedFonts folder then this means that these files are system fonts and cannot be removed, and a program of yours or a newer Version of Windows has set these fonts as system font. RegRepair 2000 is programmed to check for system fonts in the Registry but if the file is marked System with Attributes then RegRepair will not remove the font but will copy to the SavedFonts folder and mark it as a duplicate if it is duplicated.

Failed Files Not Fixed: You must read the Report carefully. You did not do what the Report said to do, you did not read the help file about the codes. There are also files that are not listed here that can fail. A program that you deleted may have written to the boot sector of the hard drive to load this files. You will then need to reinstall and uninstall that program properly. See the Exception List.

Files have been deleted that you need: You will find all the files that RegRepair deleted during repairs in a sub folder named Backup under the RegRepair 2000 folder, if you have not had RegRepair empty this folder.

RegRepair cannot shut down Windows: You may have TRS programs running, you will need to use the Ctrl-Alt-Delete to shut down programs before trying to reboot. If the Please Wait screen stays up to long, this means that Windows is writing back to the hard drive. To cure this, run a complete scandisk and defrag. If defrag tells you that you do not did need to do it now then think about this - 1% of a 2 gig hard drive is 20,000,000 clusters that windows must find before shutting down.

RegRepair runs very slow, the mouse moves rough, the video becomes corrupted or RegRepair locks up the computer. Something is running in the background like a virus scanner, a crash guard program, Norton, or some program that is monitoring the system. You must close all programs using the Ctrl-Alt-Delete buttons except for the Explorer and RegRepair.

Verifying Cabinet files hangs or you replace Extract.exe or Reinstall Windows: You will need to right click the file Extract.exe (located in the RegRepair folder) and select Properties than the program tab and Place a check mark in the "Close On Exit" box. If you have a 486 processor then the extracting and verifying of files will take a long - long time, to extract a small file (4kb) can that about 2 minutes. This means that Verifying can take 20 to 30 minutes. If RegRepair hangs during this then open NotePad and create a file named "Test.bat" and type the following replacing the D:\Win95 with the location of your cabinet files:
Extract.exe /A /D D:\Win95\ > C:\Cab.txt

Save the file to the RegRepair folder and then double click on it. You will be able to see what is wrong. If it stops at use (For Windows ME) :Extract.exe /A /D D:\Win95\ > C:\Cab.txt
(For Windows 98) :Extract.exe /A /D D:\Win95\ > C:\Cab.txt
(For Windows 95) :Extract.exe /A /D D:\Win95\ > C:\Cab.txt (If you do not have a use

If your cabinet files are in a folder more the 3 folder deep Extract many not be able to find them, this also holds true if your folder have long file names. Try moving them to C:\Windows\Options\Cabs.

Back to Table of Contents

Tech Support

If you experience any problems with RegRepair 2000 you will find the answer in the help files. Be sure to see the Troubling RegRepair section, the Exception List section. We have covered every problem that users have called us with in the help files so your answer should be at your finger tips. We strongly recommend that you print the help file out before using RegRepair 2000. You will find more help for RegRepair on our site at

Back to Table of Contents

Notes for Windows Millennium

Windows Millennium has a built in restore feature, so it is constantly monitoring the operating system. When RegRepair reads and makes any adjustments in the Registry Windows sees it. So in some case when a adjustment in the Registry is made by RegRepair and then you reboot Windows installs the default HKEY_CURRENT_USER key instead of the one that pertains to you. So you may find that your desktop is 640 X 480 and 16 color as well as your Start Menu is completely different.

If this happen reboot a few times (2 to 4 times normally works) and Windows should then install the correct Key. If not use the backup Registry in the RegRepair folder. The default location of this folder is C:\Program Files\Easy Desk Titles\RegRepair 2000\Sysbckup. Copy the 3 files to the Windows folder and paste them there so that they overwrite the existing files then reboot.

Now start over and only repair one or two errors at a time and reboot. Then make a new Bootlog and start over until all errors have been repaired. This time if you need a backup Registry use the one the RegRepair makes for you when you Repair IOS errors. The one it prompts you to make, located in the Windows folder. The files are named Classes.001, System.001, and User.001.