Items filtered by date: December 2014

When you start a Windows Vista-based computer, you may receive the following Stop error message on a blue screen:

0x0000C1F5

This issue can occur if the system file $TxfLog file has become corrupted. The Common Log File System (Clfs.sys) driver does not fix the $TxfLog file when the file becomes corrupted. In addition to the Stop error message, Windows Vista may not start until the offending disk is removed or repaired.

To resolve this issue the corrupted file needs to be repaired.

Solution 1:

This can be accomplished by booting to an installation disk that has the ability to self heal this type of issue. This can be done with a Windows 7 Beta installation disk. To recover a Windows Vista volume with Stop Error 0x0000C1F5 without data loss, perform the following steps:

1. Obtain a Windows 7 Beta or later Windows 7 installation disk
2. Insert the disk into the disk drive and boot from this Windows 7 Beta installation disk
   
   Note: Once booted, cancel out the Windows7 setup. Do not install Windows 7.
    
3. Once the system has booted successfully, remove the Windows 7 Beta installation disk and reboot the computer from the hard drive.

Note: The Windows 7 Beta installation disk includes self-healing code that resets the corrupted $TxF RM log file, therefore the problematic volume should be recovered by simply booting from the Windows 7 Beta installation disk.

Solution 2:

If solution 1 fails and gives you the same error even when you boot of the OS bootable media your only course of action is the following which will fix the probloem in all cases but has an extra step

1. remove the offending harddrive
2. attach it to a working windows PC, Vista or Windows 7 is prefered via a USB adapter (other mconnection methods might work). Connect it when windows is booted and running
3. you should see that you can see the files on the disk (might not be able to in all cases)
4. chkdsk the faulty partition / harddrive. i would check the whole disk while i was at it but most likely not required
5. chkdsk should find errors and repair them
6. done

This article covers the following scenarios when you want to backup and restore a windows profile because
you cannot just copy and then restore the profile folder

1. If you need to reinstall windows
2. you have swapped the domain you belong to
3. your domain controller goes down and needs to be replaced
4. if you want to change someones username you can use the following methods. ie when someone new comes in to do a job and the profiles are first names

All of these scenarios cause the usernames to get a new SID's that references the profile to windows and any domains so this is why you can not just copy and paste the profile they have to be 'processed' by one of the methods below.

Firstly backup the windows profile you wish to keep

To backup and restore follow one of the solutions below

Method 1

This solution only works (i think) if you still have access to the windows install

1. Insert the Windows XP CD-ROM and, in Additional Tasks you'll find " User State Migration Tool ".
2. Run it, and then import after you have added the pc to the "new" domain !

Method 2

This is not the quickest method (can be quite long) but it is reliable and just works.

1. Go to the pc logon the user, which will create the new profile
2. REBOOT the machine
3. logon as someone other then the old or new user that has administrative access to the local computer
4. right click My computer
5. click properties
6. click the advanced tab
7. click the 2nd box "user profiles" [settings]
8. copy the old profile to the new profile
9. you will also have to permit the user to have access to the folder, once that is don the user can login and have all their previous settings.

Method 3

The key is to login to windows with the user first! Windows creates a profile folder at this time and associates it with the user account. Once this folder has been created, you can delete/rename it and rename/add the correct folder in its place. Skip the Advanced user copy button thing, takes way too long. Once you get the hang of it, this process can be done in less than 5 minutes.

You might suffer permission issues with this method, i have not fully tested it.

1. Restart and logon as a local administrator or another user with admin rights.
2. Rename the C:\documents and settings\username folder to username_bak
3. Delete (or rename) any bad folders that were created in a similar manner.
4. Add user to the pc's local administrators group.
5. Login to pc with the "correctusername" or domain username.
6. Restart and logon as a local administrator or another user with admin rights.
   (Restart is necessary because if you logoff, windows will still have some of the users files locked)
7. delete the newly created profile folder c:\documents and settings\correctusername folder
8. rename the c:\documents and settings\username_bak to the name of "correctusername" (the newuserfolder)
9. Logout and login as the new user.
10. Done.

When using K9 on android you get the following messages

• failed to send some messages
• k9 java.security.cert.cetificate error

These are caused by a corrupt or expired SSL certificate stored on the phone

• go to an email account settings in k9
• set up/confirm SMTP or POP3 settings
• this re installs the SSL certificate required for secure email.

on a few windows xp (so far) the windows clock can alter itself for no reason. It seems to follow that once a day it reverts by one hour, i think this is something to do with summer / GMT time. The automatic time sync does not work either. It still maintains an hour difference. It is not bios related.

Try the following options

• change the time sync server and try a new sync
• disable firewall on router and try sync. I have found that a router for no reason can block the time sync but once it has allowed it there seems to be more issues
• Try this daylight saving patch
• Time keeps changing by itself in Windows XP
• February 2010 cumulative time zone update for Windows operating systems
  Some time patches here from microsoft
• an error occurred while windows was synchronizing with time.windows.com

when running a small network you receive the following message when connecting to a share

“No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept”.

This is caused by there not being enough slots/connections free to allow another connection. The following article show you how to fix this.

• Solution to No More Connection to a Remote Computer Problem
• Microsoft Knowledge Base Article on max connection issues
• Making registry changes to MaxMpxCt and MaxWorkItem keys when you have Windows 95 machines on your network
  This is a very indepth article and only for reference

when you run sage you get the following error

'serial and activation key combo are not valid. and you cannot change them'

solution:

• go to the account data folder and move/remove present accounts.
• you can then run the program and change the details.
• Now you can move the data files back if you want

I have had this problem numerous times in the past where the installation proceeds then ends with the messages:

During the installation of the device.
The system cannot find the file specified
and it goes into a detection loop

HERE is the solution:

Windows 2000/XP has a bug that it cannot properly detect new hardware by *.inf files, if the RunOnce registry key is missing for the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

This key is often used by installers to execute post-reboot programs, but sometimes they accidentally delete this key.

IMPORTANT: This article contains information about modifying the registry. Make sure that you understand how to backup and restore the registry, in case a problem occurs. Please read the linked Microsoft Knowledge Base article prior to editing the registry.

Go to Start » Run and enter "regedit."

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

With CurrentVersion Highlighted, go to the Edit menu and select New » Key

Name the key RunOnce, leaving everything else about the key alone.

The RunOnce key should now exist underneath the CurrentVersion key.
Once the key exists, Windows 2000/XP stops redetecting the Hardware

see also this article, Driver Install Error - "Class installer"

Note : Before trying the step below please run startup repair first

Solution :

1. Boot the computer from Vista OS DVD.

• Click on Repair Your Computer.

• Click on Command prompt.

• At the X:\Sources prompt, type bcdedit /export C:\BCD_Backup and press <Enter>

• Type c: and press <Enter>.

• At the C:\ prompt, type cd boot and press <Enter>.

• At the C:\Boot prompt, type attrib bcd -s -h -r and press <Enter>.

• At the C:\Boot prompt, type ren c:\boot\bcd bcd.old and press <Enter>.

• At the C:\Boot prompt, type bootrec /rebuildbcd and press <Enter>.

• The Boot Configuration File will be rebuilt at this point. Once it finishes, type exit and press <Enter>. Click the Restart button

Here are some other commands

bootrec /RebuildBcd - Use this option when you must completely rebuild the BCD
bootrec /FixMbr - writes a Windows Vista-compatible MBR to the system partition
bootrec /FixBoot - writes a new boot sector to the system partition by using a boot sector that is compatible with Windows Vista

If the automated startup repair doesn't do it - even after a few goes , as Prasath says,

I would try this first

1. bootrec /fixmbr

2. your dvdrom drive letter:\boot\bootsect.exe /nt60 all /force

3. del C:\boot\bcd

4. bootrec /rebuildbcd

5. Close cmd prompt

6. remove dvd, Reboot.

Fingers crossed.

You'll need to delete the registry folders for DivX from the machine (be sure to get both the local and user level folders).

To do this go to start > type 'regedit' in the run box > delete the software/divx folders from the registry of the local machine and relevant user accounts.

Once this is done run the installer file again (you do not need to uninstall first) and it will offer you the option to select an install language again. Select the correct language and complete the install as normal.

Reboot and you should find the problem corrected

Here's How:

1. Enter Windows XP Recovery Console. The Recovery Console is an advanced diagnostic mode of Windows XP with special tools that will allow you to restore the boot.ini file.

2. When you reach the command line (detailed in Step 6 in the link above), type the following command and then press Enter.

   bootcfg /rebuild
   

3. The bootcfg utility will scan your hard drives for any Windows XP installations and then display the results. Follow the remaining steps to add your Windows XP installation to the boot.ini file.

4. The first prompt asks Add installation to boot list? (Yes/No/All).

   Type Y in response to this question and press Enter.

5. The next prompt asks you to Enter Load Identifier:.

   This is the name of the operating system. For example, type Windows XP Professional or Windows XP Home Edition and press Enter.

6. The final prompt asks you to Enter OS Load options:.

   Type /Fastdetect here and press Enter.

7. Take out the Windows XP CD, type exit and then press Enter to restart your PC.

   Assuming that a missing or corrupt boot.ini file was your only issue, Windows XP should now start normally.