Sometimes you can not run Regedit. This is due to a setting in the registry itself.

When you try to run Regedit, you get a message like “Registry editing has been disabled by your administrator” or something similar.

To resolve this run the following command:

REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System /v DisableRegistryTools /t REG_DWORD /d 0 /f

This should get you the instant result.

When you are loaded up from WinXP boot CD, you can edit registry on existing installation on the HDD.

  1. Start Regedit.
  2. Go to HKEY_USERS
  3. Select File -> Load Hive.  Point to C:\Windows\System32\Config. Inside this folder select one of the files i.e software, SAM, system etc.
  4. Type new name for the folder to mount the remote registry… like REMOTE_System or REMOTE_Software.
  5. Now remote registry is loaded into regedit and you can change things there just like in normal registry.
  6. After done changes, you MUST unload the hives: File -> Unload Hive.

Check HKEY_USERS\Remote_Software\Microsoft\Windows NT\CurrentVersion\Winlogon

Shell entry must be pointing to Explorer.exe.

Userint should point to C:\Windows\System32\Userinit.exe

Boot from Linux CD with ntchpw utility installed. Most of the time I used PING. Pretty sure most of Live CD’s do have that utility.

Mount Windows partition to Linux:
ntfs-3g /dev/hda1 /mnt/ntfs
OR
mount -t ntfs-3g /dev/hda1 /mnt/ntfs -o force
The last one is used if windows did not shut down properly.
In Windows partition Navigate to WINDOWS/system32/config
Execute chntpw SAM. As a safety measure you can copy SAM file somewhere available to restore, if things go wrong.
This utility will ask you number of options. Blank the password, do not set a new one. Agree to write hive files when finish.
Restart computer to boot into Windows.

By default chntpw is loading administrator account. You can load another user if required. Read man page for chntpw to figure out how to do this.

Start cmd as Administrator. To check MTU issue:
netsh interface ipv4 show subinterfaces
This will give you a list of network adapters with MTU

To change the MTU issue following
netsh interface ipv4 set subinterface "YYY" mtu=xxxx store=persistent

Where “YYY” is a network interface name like “Wireless Network Connection”.

After uninstalling Vista SP1 you may get the yellow triangle error for
the wan miniport (SSTP). You can’t uninstall wan miniport (SSTP) or
delete it.

This is the solution:
Use the following commands to be carried out as the user Administrator
(Run as Administrator) from Command prompt (cmd):
netcfg -e -u ms_sstpminiport

You may have to find the course Hardware ID device from the Device
Manager and selecting the Details tab-> Hardware IDs if it is not
‘ms_sstpminiport’ which is causing the problem.

Taken from: Here

Vodafone VMC Lite does not want to connect to the network if if is executed under Windows XP user with restricted privileges. The software comes up, but saying “No device” and no chance to connect.

How to resolve this: Login as Administrator, Uninstall VMC Lite and install full featured VMC software from Vodafone. Connect to the network. Then login as user and try to connect again – it should work now.

Bear in mind that WinXP is treating every USB port available as separate instance, not connected to each other.. so being logged in as Administrator plug in USB modem to every available port and connect. Otherwise you’ll hear moans from users saying modem is not working.

Simple solution, but I’ve spent quite a time to figure out the way.
RIP Vodafone -)

Sometimes you need to remove device driver manual, because Device Manager in Windows does not want to remove anything and gives you “Error 31”.
If this is your case, this is the guide for you. I’ve spent a sleepless night trying to figure out how to fix this problem..
In my case that was Network Adapter Drivers that did not want to work. Wireless adapter did have a yellow triangle and in properties it showed Error 31. All the attempts to remove the device or driver did not work – the device just appeared again. So I had to manually remove the drivers.

Run device manager find your driver file and *.inf file are used by this device.
55577595
55577595

For driver files you have to read providers. If provider is Microsoft you can’t touch driver and
driver service – you can only remove non-system drivers

Remove registry folder:
HKLM\System\CurrentControlSet\Services\

Next remove driver files (*.dll,*.sys) ,*.inf file relate to your device you can find in

C:\Windows\inf\<inf_name>.inf
C:\Windows\inf\
<inf_name>.pnf
C:\Windows\system32\drivers\<driver_name>.sys
C:\Windows\System32\DriverStore\FileRepository\
<driver_name>

Don’t forget to do full backup of registry and not completely delete driver files, but misplace them: put in C:\tmp

Information taken from this discussion: http://www.vistaheads.com/forums/microsoft-public-windows-vista-general/440447-error-31-about-6t04-wifi-adapter.html

Problem: Vista can not connect to wireless network.. the system can not see the DHCP server in router and getting 169.254.x.x ip address which is private and no use at all.
To resolve this go to registry, find
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{GUID}
Where GUID is a id for that network adapter – you will see the difference if another one is wired and connected.
Add new entry (DWORD 32), call it DhcpConnDisableBcastFlagToggle and assign value 1.
Change entry DhcpConnForceBroadcastFlag to 0.
Try to reconnect.