Error 8000FFFF in Windows Vista Auto-Update

Ey guys, it’s been awhile. And it’s also been awhile since I was bugged with problems with Vista. Your computer may get an error 8000FFF when doing Automatic Updates in Windows Vista. Culprit is most probably the incorrect reporting of the system with 4GB of memory.

To fix this issue, do the following steps:

1. Run cmd [command prompt] as administrator.

2. Type: “reg delete HKLM\Components /v AdvancedInstallersNeedResolving” and then hit Enter.

3. Press “Y” to confirm.

4. Restart your computer and you should be able to run Automatic Updates again.

How to Change Your Forgotten Windows Password Using a Linux OS Disc

Yup! That’s right. Never thought it could be possible but it gave me the creeps when I successfully did it. The trick was actually maneuvered by a big-time geek and it’s just amazing how he was able to infuse the two opposing worlds of proprietary and open-source to work together. πŸ˜‰ Just a disclaimer on the following steps — this is hardcore!

If ever you get this annoying error message just because AD struck you in a complete surprise:

You’ll surely try to find ways and means to get into your Windows working environment. However, as Windows is not at all that friendly to common users like you, you’ll soon learn that you’re just wasting too much time on something futile. So anyway, why not give this a shot? πŸ™‚

1. Download a copy of Linux’ System Rescue CD and create an ISO image to a cd. You are free to use whatever burning application you have available in your computer.

2. After successfully creating the System Rescue CD, you’ll need to boot from it. (For real beginners: Insert the System Rescue CD into the optical drive (CD-ROM). Change the boot sequence of your drive to the optical drive in the computer’s System BIOS, save changes and restart. This should allow you to automatically boot to the disc inserted in the optical drive.)

3. Upon booting to the System Rescue CD, it will take you to a command prompt screen that looks like this:

4. Mount the hard drive using this command: ntfs-3g /dev/sda1 /mnt/windows -o force. (You can use the df -m command to verify that the drive is already mounted in the right drive. In this example, it is mounted on /mnt/windows.)

5. Change the directory into Windows/System32/config directory inside of the windows installation. Take note that the full path might differ depending on where the Windows folder installation was created. You can do that using this command: cd /mnt/windows/Windows/System32/config

6. The moment you get into that directory, you should be able to see a SAM file, which is where we will change the passwords.

7. In order to change the password, we will use the chntpw command. It’s more effective to use the -l argument first so all the usernames in the file will be listed out.

Command: chntpw -l

8. Add the -u argument with your username (kinda looks like the command below, the username used in the example is geek):

Command: chntpw -u geek SAM

This will take you to this screen:

9. At the prompt, type in your new password and don’t forget to press “y” when it prompts you to save.

10. By this time, your password should already be changed. Type the command reboot to restart the computer. Don’t forget to take the System Rescue disc.

11. Go back to the system BIOS and revert back to your original boot sequence (set it back to the HDD as the 1st boot device). Upon booting up, you should be able to see this screen and should be able to login using your new password.

Have a fun time tweaking your Windows operated computer now! By the way, this works both in Windows XP and Vista operating systems. Ciao! πŸ˜‰


Inaccessible Boot Device on Multi-Core Processor when re-Starting a Windows Vista Computer

Have you encountered this kind of blue-screen error? Irritating, huh? Well…

Just found out recently after having to experience the same BSOD for 3 times in a row. I tried googling for the answer and fortunately found a convenient explanation and fix in the Microsoft website.

As per Microsoft, the error occurs due to the race inter-lapping of threads reading and written causing a the PCI root node to be missing from the device tree. Hence, the inaccessible_boot_device because the storage is now missing. It’s kind of a brain-twister really but it goes something like that. To go through all the techie-jargons, check out the Microsoft explanation on this. πŸ˜‰

To resolve this error, download the Microsoft Hotfix.

No WPA2 Option in Dell Wireless Utility

So you have Dell computer using a Dell Wireless Card and you want to set your network security for WPA2 Encryption but sadly you don’t find any option in the Dell Wireless Utility to set it to WPA2. You double-checked your Windows Zero Configuration and found that it’s possible to choose the WPA2 Encryption. But still, you would want to use the Dell Wireless Utility since it’s the utility that came installed with your card. And you just want to make sure everything’s working alright.

Is this Dell’s fault? Do you think you have a bad Wireless Card or a bad Dell computer? Don’t fret pal, here’s the work-around instead of picking up the phone to get hold of a Dell technician:

Choose either WPA-Personal (PSK) or WPA-Enterprise in your Dell Wireless Utility. This will enable you to connect again to your network with a WPA2 Security Key setting. You can also use this when manually adding a non-broadcasting network with WPA2 configured.

Internet Connection Lost after Installing MS Security Update KB951748

Internet Connection Lost after Installing MS Security Update KB951748

This happens when you have ZoneAlarm Internet Security or Firewall installed in your computer. The moment the MS Security Update KB951748 finishes downloading and installing in your computer, your internet connection gets lost and you’ll have no idea what caused it.

Here’s the work-around:

1. You can set your ZoneAlarm Firewall Security (Internet Security Zone) from HIGH to MEDIUM.

Other known work-arounds by advanced users would be to uninstall (remove) the MS Security Update KB951748 from the Add/Remove Programs of your Control Panel (this works for Windows operating system users) and then configuring the Windows Update to Turn-off. Or you can also run System Restore then Turn-off your Windows Update afterwards.

Force Dell PC Restore thru BOOT_DSR.exe

To all Dell computer owners out there. Sometimes our computer systems bug down on us big time that the only solution for us to do is to reload the operating system to erase all our problems (only if the issue lies within the depths of the operating system); but what if you don’t have a restore disc or an operating system intallation disc? Is it the end of your world? Do you call their support trunkline?

For all you know, some Dell machines were designed with back-up recovery tool preloaded in the hard drive during its building. With features like Norton Ghost and PC Restore (or Dell Image Restore to some), reloading the operating system in our Dell machines/computers is just at the tip of our hands.

However, what if your PC Restore (which is accessible by pressing Ctrl and F11 altogether) won’t work and won’t let us do the reload? As long as the computer is booting up to Windows (even with all the errors and what-nots), you can still run Dell’s PC Restore function by manually running it from it’s location. Here’s how:

1. Run the Dell PC Restore function from this directory: C:\dell\utilities\dsrfolder.

2. It will just give you a warning, you just have to click YES and it will continue with its process by restarting the computer and boot to the PC Restore Utility.

Or, another way is clicking this executable file: BOOT_DSR.EXE. (I’m not sure though if this work-around will work with Dell systems without Norton Ghost. But heck, you could always give it a shot! πŸ˜‰ )

To learn more about Dell’s partitioning and PC Restore features, check out these websites for further reading:



Windows XP Logs Off As Soon As you Log In

Irritating? Here’s why:

Windows SA replaces userinit.exe used in logon with its own wsaupdater.exe. But uninstalling doesn’t revert it back. Some ad-aware programs may also remove or quarantine wsaupdater.exe thinking that it’s harmful.

Here’s the fix:

1. Boot using your Windows XP disc.
2. Enter Recovery Console.
3. At the ‘command prompt’ go to C:/windows/system32
4. Next type the command: copy userinit.exe wsaupdater.exe
5. Exit and reboot normally. You should now be able to logon. But you’re not done yet. πŸ˜‰
6. Run regedit.
7. Find the Userinit key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
8. Modify the entry:
C:\WINDOWS\System32\wsaupdater.exe, (DO NOT FORGET THE COMMA ΓΌ)
So that it reads:
C:\WINDOWS\System32\userinit.exe, (DO NOT FORGET THE COMMA ΓΌ)

Hope this helps! πŸ˜‰