Jump to content
Sign in to follow this  
Rbreb13

Fixes: If its broke the fix might be in here

Recommended Posts

This thread will be dedicated to fixes for any and all problems. Hardware, software, security or whatever. It is locked so as not to clutter up the fixes with replies. If you have a fix that you think would be useful, please PM me or Bruceleeon and we will see that it gets posted and credit given to the contributor.

Thank you for your cooperation!

Share this post


Link to post
Share on other sites

Norton SystemWorks: installation problem in Windows XP.

Error: "Install 2002 Error: 1402 Could not open key: SoftwareMicrosoftWindowsCurrentVersionSharedDLLs. Verify that you have sufficient access to that key or contact your support personnel" during the installation of Norton AntiVirus

Situation:

When you attempt to install Norton AntiVirus 2002 (NAV), you see the following error message, and the installation will not continue:

"Install 2002 Error: 1402 Could not open key: SoftwareMicrosoftWindowsCurrentVersionSharedDLLs. Verify that you have sufficient access to that key or contact your support personnel."

Solution:

In some reported cases, this behavior has been caused by a virus, Trojan, or worm infection. Follow the instructions in the document How to remove a virus from your computer when Norton AntiVirus is not yet installed to insure that the computer is not infected.

If the computer is not infected and you are running Windows XP, then this error most often occurs because access permissions are not set correctly in the registry. This is frequently caused by upgrading the computer to Windows XP without first uninstalling NAV, though the problem can also occur when installing NAV on a computer that has Windows XP Home installed. Also, in some cases this error can be corrected by creating a password on the Administrator account.

Follow the steps in the sections below in the order listed to fix the problem.

To set the permissions correctly:

1. Use the Registry Editor to open the permissions dialog box for the Symantec registry key:

a. Click Start, and then click Run.

b. In the Run dialog box, type regedit and then click OK. The Registry Editor appears.

CAUTION: We strongly recommend that you back up the registry before making any changes to it. Incorrect changes to the registry can result in permanent data loss or corrupted files. Modify only the keys that are specified. See the document How to back up the Windows registry for instructions.

c. Navigate to the following key:

HKEY_LOCAL_MACHINESOFTWARESymantec

d. Right-click the key, and then click Permissions. The "Permissions for Symantec" dialog window appears.

2. Set the permissions:

For Windows XP Professional:

a. Choose the Administrators account. This step displays the "Permissions for Administrators" dialog box.

b. Confirm that the Full Control box is checked in the Allow column.

For Windows XP Home and XP Professional:

a. Choose the SYSTEM account. This step displays the "Permissions for SYSTEM" dialog box.

b. Confirm that the Full Control box is checked in the Allow column.

c. Choose the CREATOR OWNER account. This step displays the "Permissions for CREATOR OWNER" dialog box.

d. Confirm that the Full Control box is checked in the Allow column.

3. Configure advanced options:

a. Click the Advanced button, and then click the Permissions tab.

b. Confirm that the Administrators, CREATOR OWNER, and SYSTEM accounts have their permissions set to Full Control in the "Permissions entries" box.

c. Confirm that the option "Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here" is checked.

d. Check the option "Replace permission entries on all child objects with entries shown here that apply to child objects."

4. Click Apply.

5. Click OK, click OK again, and then close the Registry Editor.

6. Reinstall NSW.

If these steps do not fix the problem, then go on to the next section.

To create a password for the Administrator account:

1. Restart the computer in Safe mode and create a password for your Administrator account.

A. Restart your computer in Safe mode:

1. Click Start, and then click Shut Down.

2. Click Turn Off Computer. In the drop-down menu, click Restart.

3. As the computer restarts, press F8.

4. Choose Safe mode, and then press Enter.

5. When the Windows Welcome screen appears, log on as Administrator.

B. Click Start, and then click Control Panel.

C. Click User Accounts, and then click Change an Account.

D. Click the Administrator account under the Pick an account to change section.

E. Click Create a password.

F. Follow the steps to add a password. Click OK.

2. Restart the computer, and then log on as Administrator.

3. Reinstall NSW.

Additional Information:

This problem may also occur as a result of incorrect, invalid, or corrupt entries in the registry, possibly due to left-over registry entries from previous installations of NAV. For more information, see the information at the following Microsoft Web page: Click Here

Symantec/Norton SystemWorks cleanup utility (SymClean) for uninstalling if it doesn't show in Add/Remove Programs:

Click here

Share this post


Link to post
Share on other sites

Outlook 2000

OL2000: Error Message: "Cannot Start Outlook" on Windows NT Workstation

--------------------------------------------------------------------------------

The information in this article applies to:

Microsoft Outlook 2000

--------------------------------------------------------------------------------

IMPORTANT : This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

When you attempt to start Outlook for the first time after installing Microsoft Office 2000, you receive the following error message even though you are logged on as the administrator, or as a member of the local Administrator group, on the Microsoft Windows NT 4.0 Workstation computer:

Cannot start Microsoft Outlook. Outlook could not be configured, because Administrator privileges are required for you to install some types of software on this computer. Before you can use Outlook, you must either log on to your computer as an Administrator and finish configuring Outlook, or ask your System Administrator to configure Outlook e-mail support for you."

CAUSE

You do not have sufficient permissions on the following registry key:

HKEY_LOCAL_MACHINESoftwareMicrosoftOffice9.0OutlookSetup

RESOLUTION

Change the permissions on the registry key to Full Control.

MORE INFORMATION

WARNING : Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

To set the permissions to Full Control, follow these steps:

Log on as the local administrator or member of the Administrator group.

On the Start menu, click Run . In the Open box, type Regedt32 to run the Registry Editor. Click OK . Regedt32.exe must be used, rather than Regedit.exe, to make Security changes.

On the Window menu, click HKEY_LOCAL_MACHINE on Local Machine .

Navigate to the following registry key:

SoftwareMicrosoftOffice9.0OutlookSetup

On the Security menu, click Permissions .

Click the <computer name>Administrators group, and on the Type of Access list, click to select Full Control (where <computer name> is the computer you are logged on to).

Click OK , and on the Registry menu, click Exit .

Restart Outlook. The first-run portion of Setup for Outlook will complete without further error.

Making this security change while logged in as administrator will also affect any user who is a member of the Administrator group.

Share this post


Link to post
Share on other sites

DVD Region Killer v2.3.0.1 [830k] W9x/2k/XP FREE

http://home.t-online.de/home/CloneCD/downl...etupRegKill.exe

http://www.elby.org/RegionKiller/english/

"[This] enables you to play DVD titles made for different regions on your PC, without the hassle of switching the region of your DVD player software. As you probably know, a DVD is usually mastered to play in a specific region of the world. The world is divided into 6 regions, for example USA is region 1, and Europe is region 2. A DVD mastered to play in the US (region 1) will not be played on a DVD player set to region 2 (Europe). There are many reasons why the DVD Industry has set up this region restriction, but there are various reasons to overcome this restriction, too. For example, a lot of people are offended by 'forced subtitles,' when they prefer to watch a movie in their original language, just to name one."

Recommend

Share this post


Link to post
Share on other sites

Direct X fix Wrong Version.

I found a way to bypass the wrong version error

qoute from crash override (over at rage3d forum)

Here is how to fix that :

1)Click on your start button

2)Click on the run button

3)Type in regedit

4)Goto HKEY_LOCAL_MACHINESOFTWAREMicrosoftDirectX

5)In there you will see a KEY that says Version

6)Modify this to 4.08.01.0810

7)close down regedit reboot

Share this post


Link to post
Share on other sites

I was having a problem with a Promise Ultra 100 ATA controller card. Windows was only seeing the Hard drive attached to it about 1/2 the time. Windows said the driver was fine. Thanks to a suggestion from Bruceleeon (Our Illustrious Leader) to "FORCE" Windows XP Pro to accept a newer driver it is working perfectly now.

Lesson: Do NOT trust Windows to make the correct decision for you!

Share this post


Link to post
Share on other sites

Disable Error Reporting

There is some benefit to allowing Win XP to send the error report to Microsoft; the company can see whether a patch is needed to make Win XP more compatible with applications. On the other hand, if your programs do this often enough, having to answer the error-report prompt constantly gets annoying.

If you right-click on My Computer and select Properties or open the System icon in the Control Panel, you'll see the System Properties dialog. Select the Advanced tab and click on Error Reporting. This brings up a dialog that lets you disable error reporting altogether. Even better, click on Choose Programs and disable error reporting for specific programs. That way, if you have an application that causes a lot of errors and you've already sent Microsoft half a dozen reports, you can disable the feature for that program and never see the prompts again.

Share this post


Link to post
Share on other sites

Let's say you want to see all of the images sitting inside a certain folder. Sure, I suppose you could open all of them in your favorite graphics viewer. That might take a while, though. Best use Explorer's built-in thumbnail feature. Is disk speed an issue? What about disk space? Both are valid concerns, but they can be addressed easily with a little Registry diving. Alter the pixel size and quality of all thumbnails by navigating to HKEY_LOCAL_MACHINE Software Microsoft Windows CurrentVersion Explorer. To change the size for each thumbnail, add a DWORD value and label it "ThumbnailSize" (sans quotes). This entry should be given a number between 32 and 256; I suggest 50 (instead of the default 100). To change the image quality of thumbnails, add a DWORD value and label it "ThumbnailQuality" (sans quotes). This entry should be given a number between 50 and 100; I suggest changing this one to 50 to start with, too. The next time you switch a folder to thumbnail view, your changes should be applied. Hold onto the SHIFT key when you select the "Thumbnail" option from the view menu if you want to turn off file names (to save screen space). SHIFT click again to turn 'em back on. Remember: you can also turn off thumbnail disk caching through the Folder Options dialog. In the Windows Explorer, click Tools | Folder Options | View | Do not cache thumbnails.

Thanks to Lockergnome.

Share this post


Link to post
Share on other sites

DirectX 9 and Windows Messenger

"WinXP users who download and install DirectX 9 from MS may find that their Windows Messenger doesn't work afterwards, either hanging, crashing out or giving a 'memory could not be read' error. 

"After a lot of digging, it turns out that this is due to a chain of events. Windows Messenger makes a call to DirectPlay (in DirectX) to register things such as voice calling and multiplayer games and remote assistance. DirectPlay tries to open ports on the router to do this, so it asks the DirectPlay UPNP helper which sends a request to your router to open the ports. Now, it just so happens that some Linksys routers don't negotiate this right and so I assume what gets returned to DirectPlay and/or Messenger isn't what it's expecting and so Messenger crashes. The solution is to upgrade the firmware on the Router to the latest available, which for my BEFSR41 is 1.44.2. After doing that everything magically works again. Messenger wouldn't work with any of my archived versions of the firmware, *only* the latest posted one..." 

Editor's Note: The release notes for the firmware release mentioned does specifically note UPNP issues as being the reason for the update. The Linksys routers have UPNP enabled by default, as does Windows XP. I recommend disabling UPNP across the board because of these sorts of compatibility issues that seem to be fairly common. There have also been security issues related to UPNP within Windows XP. 

Furo's 89th Law: The more automated it is, the more difficult the troubleshooting process when things inevitably blow up. Without the firmware release from Linksys, how would anyone determine that this was a router problem? Linksys would likely be the last one called for a Windows application crash. 

Credit for above to Lockergnome

Share this post


Link to post
Share on other sites

You Cannot Install Updates or You Are Prompted to Install Updates That You Have Already Installed

SYMPTOMS

When you try to configure an automatic update, to install an update, or to install a service pack on your Windows XP-based computer, you may experience one or more of the following behaviors:

You cannot install certain updates.

You are prompted to install one or more updates that you have already installed.

When you use the Windows Update Web site to install updates, you may receive a 643 error message or a message that indicates that Windows Update was not able to complete the operation.

Microsoft Windows Media Player may be slow to respond.

The %WINDIR%system32CatRoot2Edb.log may grow to 20 megabytes (MB) even though the file is typically only 5,120 kilobytes (KB).

When you try to install an update, you may receive an error message that is similar to one of the following:

Setup could not verify the integrity of the file Update.inf. Make sure the Cryptographic service is running on this computer.

-or-

Failed to install catalog files.

-or-

The software you are installing has not passed Windows Logo testing to verify it's compatibility with Windows XP. (Tell me why this testing is important.)

This software will not be installed. Contact your system administrator.

When you try to install a Windows XP service pack, you may receive an error message that is similar to the following:

Service Pack 1 Setup could not verify the integrity of the file. Make sure the Cryptographic service is running on this computer

RESOLUTION

To resolve this behavior, use one or more of follow these methods.

Method 1: Rename the Edb.log File

To resolve this behavior, rename the Edb.log file, and then reinstall the update. To rename the Edb.log file, follow these steps:

1. Right-click Start and then click Explore.

2. Locate the following file: C:WINDOWSSystem32Catroot2Edb.log

3. Right-click the Edb.log file, and then click Rename.

4. Type edb.old, and then press ENTER.

5. If you receive a message that prompts you to confirm the rename operation, click Yes.

6. Quit Windows Explorer.

Method 2: Set Cryptographic Services to Automatic

Set the Cryptographic Services to Automatic, and then try to reinstall the update. To set the Cryptographic Services to Automatic, follow these steps:

1. Start the Administrative Tools utility in Control Panel.

2. Double-click Services.

3. Right-click Cryptographic Services, and then click Properties.

4. Click Automatic for Startup type, and then click Start.

Method 3: Rename the Catroot2 Folder

Rename the Catroot2 folder, and then reinstall the update. To rename the Catroot2 folder, use Procedure 1 or Procedure 2.

If these first two procedures do not resolve the behavior, use Procedure 3 to register .dll files.

Procedure 1

1. Quit all programs that are running, including antivirus programs.

2. Right-click Start, and then click Explore.

3. Locate the C:WindowsSystem32Catroot2 folder.

4. Right-click the Catroot2 folder, and then click Rename.

5. Type a new name for the folder, for example Oldcatroot2, and then press ENTER.

6. Quit Windows Explorer.

Procedure 2

1. Click Start, and then click Run.

2. In the Open box, type cmd, and then click OK.

3. At the command prompt, type the following commands, pressing ENTER after each line:

net stop cryptsvc

ren %systemroot%system32catroot2 oldcatroot2

net start cryptsvc

exit

Procedure 3

To register .dll files, follow these steps:

1. Click Start, and then click Run.

2. In the Open box, type cmd, and then click OK.

3. At the command prompt, type the following commands, pressing ENTER after each line:

Note Click OK to the message if prompted.

regsvr32 /u softpub.dll

regsvr32 /u wintrust.dll

regsvr32 /u initpki.dll

regsvr32 /u dssenh.dll

regsvr32 /u rsaenh.dll

regsvr32 /u gpkcsp.dll

regsvr32 /u sccbase.dll

regsvr32 /u slbcsp.dll

regsvr32 /u cryptdlg.dll

regsvr32 softpub.dll

regsvr32 wintrust.dll

regsvr32 initpki.dll

regsvr32 dssenh.dll

regsvr32 rsaenh.dll

regsvr32 gpkcsp.dll

regsvr32 sccbase.dll

regsvr32 slbcsp.dll

regsvr32 cryptdlg.dll

exit

Method 4: Use the System File Checker (SFC) Command

1. Click Start, and then click Run.

2. In the Open box, type cmd, and then click OK.

3. At the command prompt, type sfc /purgecache and then press ENTER.

Note To run this command, you may require access to the Windows installation source files. You will receive the following message at the command prompt when this command has completed:

Windows File Protection successfully made the requested change.

4. At the command prompt, type sfc /scannow, and then press ENTER.

Note This command will take several minutes to complete and may require access to the Windows installation source files. When the command has completed, type exit to close the command prompt.

5. Try again to install the updates to Windows. If the problem is resolved, do not continue with the remaining steps in this section.

6. Perform an in-place upgrade (reinstallation) of Windows XP.

For additional information, search the following article number to view the article in the Microsoft Knowledge Base:

315341 How to Perform an In-Place Upgrade (Reinstallation) of Windows XP

7. Reinstall all updates to Windows.

MORE INFORMATION

For additional information about how to configure automatic updates in Windows XP, search the following article number to view the article in the Microsoft Knowledge Base:

306525 HOW TO: Configure and Use Automatic Updates in Windows XP

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×