• Category Archives ToolBox posts
  • Outlook 2013 | 2010 – Export-Import Auto Fill / Auto Complete data

    https://kb.wisc.edu/helpdesk/page.php?id=38759

    https://kb.wisc.edu/helpdesk/page.php?id=39592

    EXPORT

    How to locate and save the “Auto Complete file” in Outlook 2010/2013 for Windows 7/8.1.

      1. Open Start Menu.
        • Win 7: Select the Windows Start Button.
        • Win 8/8.1: Press the Start Button on your keyboard to launch the Windows 8 tile menu or hover your cursor toward the lower left corner of your window to make the Start Button appear.
    Windows 7 Windows 8/8.1
    Windows 7 Start button Windows 8 Start button
      1. Double-click on Computer if using Windows 7, for Windows 8/8.1 users type Computer and select the Computer tile
        • Windows 7

    Windows 7 Computer folder

        • Windows 8/8.1

    Computertile

      1. Double-click on Local disk C:

    Windows 8 Local Disk C

      1. Double-click on Users folder.

    Users folder

      1. Double-click on Username of the target user.

    Users Profile

      1.  Double-click on the AppData folder.
        • Must have administrative privileges

    AppData folder

      1. Double-click on the Local folder.

    Local folder

      1. Double-click on Microsoft folder.

    Microsoft folder

      1. Double-click on Outlook.

    Outlook folder

      1. Double-click on RoamCache.

    RoamingCache folder

      1. The file that starts with Stream_Autocomplete_**** contains the Autocomplete file used in Office 2013.

    Stream_AutoComplete File>

    1. Save this file to a flash drive or other media target and use it to import the Auto Complete names into another Outlook 2013 account.

     

    IMPORT

      1. Quit Outlook.
      2. Open the Start Menu.
        • Win 7: Select the Windows Start Button.
        • Win 8/8.1: Press the Start Button on your keyboard to launch the Windows 8 tile menu or hover your cursor toward the lower left corner of your window to make the Start Button appear.
        Windows 7 Windows 8/8.1
        Windows 7 icon Windows 8.1 start icon
      3. Double-click on Computer if using Windows 7, for Windows 8/8.1 users type Computer and select the Computer tile
        • Windows 7

          Windows 7 Computer folder

        • Windows 8/8.1

          Computer tile

      4. Open Local Disk (C:).

        Local Disk C

      5. Open Users.

        Users

      6. Open the folder of the User Account you are servicing.

        User folder

      7. Open App Data (Must have Admin privileges). The AppData folder is a hidden folder, to see hidden folders please refer to our Windows 7 & 8 – Show Hidden Files and Folders documentation.

        AppData folder

      8. Open the Local folder.

        AppData Local folder

      9. Open Microsoft.

    Microsoft folder

      1. Open Outlook.

    Outlook folder

    1. Open RoamCache.

      RoamingCache folder

    2. Copy the existing file name to the clipboard or a text file.
    3. Rename the Stream_Autocomplete…. file in this folder to “oldStreaming_autocomplete…..”
    4. Copy the source file you saved from your other computer or Outlook version into this folder and name it the same name as the original file name from the step above.

  • Windows XP – How to Repair Errors that Prevent Windows from Booting

    https://kb.wisc.edu/helpdesk/page.php?id=5836

    Try Booting Last Good Known Configuration

    1. Start the computer and hit F8 at the BIOS screen.
    2. Select Last Known Good Configuration (your most recent settings that worked) from the “Windows Advanced Options Menu”.
    3. If the computer still won’t boot, continue to the next section.

    Repair the Windows Installation from the Recovery Console

    This section references “Repairing Windows XP in Eight Commands” by Robert Hallock (2006). See http://icrontic.com/articles/repair_windows_xp for the full text of that article.

    1. Boot from a standard Windows XP Install CD (not a Network Install CD).
    2. At the first setup screen, hit R to repair Windows using the Recovery Console.
    3. Select the Windows installation that you would like to repair by entering its number, followed by Enter.
    4. At the Recovery Console, type each following commands followed by Enter:
      • CD ..
      • ATTRIB -H C:\\boot.ini
      • ATTRIB -S C:\\boot.ini
      • ATTRIB -R C:\\boot.ini
      • del boot.ini
      • BOOTCFG /Rebuild
        • Set the Load Identifier to: Microsoft Windows XP Professional
        • Set the OS Load Options to: /noexecute=optin /fastdetect
      • CHKDSK /R
      • FIXBOOT
    5. Type exit to reboot the computer.

  • 10 things you can do when Windows XP won’t boot

    http://www.techrepublic.com/blog/10-things/10-things-you-can-do-when-windows-xp-wont-boot/

     

    10 things you can do when Windows XP won’t boot

    If your computer powers up okay, but the Windows XP operating system won’t boot properly, you have some troubleshooting ahead of you. Here’s a look at the likely culprits and what you can do to fix the problem.

     

    When your computer hardware appears to power up okay, but the Windows XP operating system won’t boot properly, you have to begin a troubleshooting expedition that includes getting into the operating system, determining the problem, and then fixing it. To help you get started on this expedition, here are 10 things you can do when Windows XP won’t boot.

    This blog post is available in PDF format as a TechRepublic Download. This entry was originally published as an article on January 26, 2006.

    #1: Use a Windows startup disk

    One of the first things you should reach for when troubleshooting a Windows XP boot problem is a Windows startup disk. This floppy disk can come in handy if the problem is being caused when either the startup record for the active partition or the files that the operating system uses to start Windows have become corrupted.

    To create a Windows startup disk, insert a floppy disk into the drive of a similarly configured, working Windows XP system, launch My Computer, right-click the floppy disk icon, and select the Format command from the context menu. When you see the Format dialog box, leave all the default settings as they are and click the Start button. Once the format operation is complete, close the Format dialog box to return to My Computer, double-click the drive C icon to access the root directory, and copy the following three files to the floppy disk:

    • Boot.ini
    • NTLDR
    • Ntdetect.com

    After you create the Windows startup disk, insert it into the floppy drive on the afflicted system and press [Ctrl][Alt][Delete] to reboot the computer. When you boot from the Windows startup disk, the computer will bypass the active partition and boot files on the hard disk and attempt to start Windows XP normally.

    #2: Use Last Known Good Configuration

    You can also try to boot the operating system with the Last Known Good Configuration feature. This feature will allow you to undo any changes that caused problems in the CurrentControlSet registry key, which defines hardware and driver settings. The Last Known Good Configuration feature replaces the contents of the CurrentControlSet registry key with a backup copy that was last used to successfully start up the operating system.

    To use the Last Known Good Configuration feature, first restart the computer by pressing [Ctrl][Alt][Delete]. When you see the message Please select the operating system to start or hear the single beep, press [F8] to display the Windows Advanced Options menu. Select the Last Known Good Configuration item from the menu and press [Enter].

    Keep in mind that you get only one shot with the Last Known Good Configuration feature. In other words, if it fails to revive your Windows XP on the first attempt, the backup copy is also corrupt.

    #3: Use System Restore

    Another tool that might be helpful when Windows XP won’t boot is System Restore. System Restore runs in the background as a service and continually monitors system-critical components for changes. When it detects an impending change, System Restore immediately makes backup copies, called restore points, of these critical components before the change occurs. In addition, System Restore is configured by default to create restore points every 24 hours.

     

    To use System Restore, first restart the computer by pressing [Ctrl][Alt][Delete]. When you see the message Please select the operating system to start or hear the single beep, press [F8] to display the Windows Advanced Options menu. Now, select the Safe Mode item from the menu and press [Enter].

    Once Windows XP boots into Safe mode, click the Start button, access the All Programs | Accessories | System Tools menu, and select System Restore. Because you’re running in Safe mode, the only option on the opening screen of the System Restore wizard is Restore My Computer To An Earlier Time, and it’s selected by default, so just click Next. Then, follow along with the wizard to select a restore point and begin the restoration procedure.

    #4: Use Recovery Console

    When a Windows XP boot problem is severe, you’ll need to use a more drastic approach. The Windows XP CD is bootable and will provide you with access to a tool called Recovery Console.

    To boot from the Windows XP CD, insert it into the CD-ROM drive on the problem system and press [Ctrl][Alt][Delete] to reboot the computer. Once the system begins booting from the CD, simply follow the prompts that will allow the loading of the basic files needed to run Setup. When you see the Welcome To Setup screen, shown in Figure A, press R to start the Recovery Console.

    Figure A

    Recovery console

    You’ll then see a Recovery Console menu, like the one shown in Figure B. It displays the folder containing the operating system’s files and prompts you to choose the operating system you want to log on to. Just press the menu number on the keyboard, and you’ll be prompted to enter the Administrator’s password. You’ll then find yourself at the main Recovery Console prompt.

    Figure B

    Choose your OS

    #5: Fix a corrupt Boot.ini

    As the Windows XP operating system begins to load, the Ntldr program refers to the Boot.ini file to determine where the operating system files reside and which options to enable as the operating system continues to load. So if there’s a problem rooted in the Boot.ini file, it can render Windows XP incapable of booting correctly.

    If you suspect that Windows XP won’t boot because Boot.ini has been corrupted, you can use the special Recovery Console version of the Bootcfg tool to fix it. Of course, you must first boot the system with the Windows XP CD and access the Recovery Console as described in #4.

    To use the Bootcfg tool, from the Recovery Console command prompt, type

    Bootcfg /parameter

    Where /parameter is one of these required parameters:

    • /Add—Scans the disk for all Windows installations and allows you to add any new ones to the Boot.ini file.
    • /Scan—Scans the disk for all Windows installations.
    • /List—Lists each entry in the Boot.ini file.
    • /Default—Sets the default operating system as the main boot entry.
    • /Rebuild—Completely re-creates the Boot.ini file. The user must confirm each step.
    • /Redirect—Allows the boot operation to be redirected to a specific port when using the Headless Administration feature. The Redirect parameter takes two parameters of its own, [Port Baudrate ] | [UseBiosSettings].
    • /Disableredirect—Disables the redirection.

    #6: Fix a corrupt partition boot sector

    The partition boot sector is a small section of the hard disk partition that contains information about the operating system’s file system (NTFS or FAT32), as well as a very small machine language program that is crucial in assisting the operating system as it loads.

    If you suspect that Windows XP won’t boot because the partition boot sector has been corrupted, you can use a special Recovery Console tool called Fixboot to fix it. Start by booting the system with the Windows XP CD and accessing the Recovery Console as described in #4.

    To use the Fixboot tool, from the Recovery Console command prompt, type

    Fixboot [drive]:

    Where [drive] is the letter of the drive to which you want to write a new partition boot sector.

    #7: Fix a corrupt master boot record

    The master boot record occupies the first sector on the hard disk and is responsible for initiating the Windows boot procedure. The master boot record contains the partition table for the disk as well as a small program called the master boot code, which is responsible for locating the active, or bootable, partition, in the partition table. Once this occurs, the partition boot sector takes over and begins loading Windows. If the master boot record is corrupt, the partition boot sector can’t do its job and Windows won’t boot.

    If you suspect Windows XP won’t boot because the master boot record has been corrupted, you can use the Recovery Console tool Fixmbr to fix it. First, boot the system with the Windows XP CD and access the Recovery Console as described in #4.

    To use the Fixmbr tool, from the Recovery Console command prompt, type

    Fixmbr [device_name]

    Where [device_name] is the device pathname of the drive to which you want to write a new master boot record. For example, the device pathname format for a standard bootable drive C configuration would look like this:

    DeviceHardDisk0

    #8: Disable automatic restart

    When Windows XP encounters a fatal error, the default setting for handling such an error is to automatically reboot the system. If the error occurs while Windows XP is booting, the operating system will become stuck in a reboot cycle—rebooting over and over instead of starting up normally. In that case, you’ll need to disable the option for automatically restarting on system failure.

    When Windows XP begins to boot up and you see the message Please select the operating system to start or hear the single beep, press [F8] to display the Windows Advanced Options Menu. Then, select the Disable The Automatic Restart On System Failure item and press [Enter]. Now, Windows XP will hang up when it encounters the error and with any luck, it will display a stop message you can use to diagnose the problem.

    #9: Restore from a backup

    If you can’t seem to repair a Windows XP system that won’t boot and you have a recent backup, you can restore the system from the backup media. The method you use to restore the system will depend on what backup utility you used, so you’ll need to follow the utility’s instructions on how to perform a restore operation.

    #10: Perform an in-place upgrade

    If you can’t repair a Windows XP system that won’t boot and you don’t have a recent backup, you can perform an in-place upgrade. Doing so reinstalls the operating system into the same folder, just as if you were upgrading from one version of Windows to another. An in-place upgrade will usually solve most, if not all, Windows boot problems.

    Performing a Windows XP in-place upgrade is pretty straightforward. To begin, insert the Windows XP CD into the drive, restart your system, and boot from the CD. Once the initial preparation is complete, you’ll see the Windows XP Setup screen (shown earlier in Figure A). Press [Enter] to launch the Windows XP Setup procedure. In a moment, you’ll see the License Agreement page and will need to press [F8] to acknowledge that you agree. Setup will then search the hard disk looking for a previous installation of Windows XP. When it finds the previous installation, you’ll see a second Windows XP Setup screen, as shown in Figure C.

    Figure C

    In-place upgrade

    This screen will prompt you to press R to repair the selected installation or to press [Esc] to install a fresh copy of Windows XP. In this case, initiating a repair operation is synonymous with performing an in-place upgrade, so you’ll need to press R. When you do so, Setup will examine the disk drives in the system. It will then begin performing the in-place upgrade.

    Keep in mind that after you perform an in-place upgrade or repair installation, you must reinstall all updates to Windows.


  • Use the System File Checker tool to repair missing or corrupted system files

    https://support.microsoft.com/en-us/kb/929833

    System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. This article describes how to run the System File Checker tool (SFC.exe) to scan your system files and to repair missing or corrupted system files. If a Windows Resource Protection (WRP) file is missing or is corrupted, Windows may not behave as expected. For example, some Windows functions may not work, or Windows may crash.

    Run the System File Checker tool (SFC.exe)

    To do this, follow these steps:

    1. Open an elevated command prompt. To do this, do the following as your appropriate:
      Windows 8.1 or Windows 8

      Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. Type Command Prompt in the Search box, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
      A screenshot for this step.

      Windows 10, Windows 7, or Windows Vista

      To do this, click Start, type Command Prompt or cmd in the Search box, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
      A screenshot for this step.

    2. At the command prompt, type the following command, and then press ENTER:

      sfc /scannow

      A screenshot for this step.

      The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache.
      The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows.

      Note Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished.

    3. After the process is finished, you may receive one of the following messages:
      • Windows Resource Protection did not find any integrity violations.

        This means that you do not have any missing or corrupted system files.

      • Windows Resource Protection could not perform the requested operation.

        To resolve this problem, perform the System File Checker scan in safe mode, and make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp.

      • Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log%WinDir%\Logs\CBS\CBS.log.

        To view the detail information about the system file scan and restoration, go to How to view details of the System File Checker process.

      • Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log%WinDir%\Logs\CBS\CBS.log.

        To repair the corrupted files manually, view details of the System File Checker process to find the corrupted file, and then manually replace the corrupted file with a known good copy of the file.

    More information
    How to view details of the System File Checker process

    To view the details that included in the CBS.Log file, you can copy the information to the Sfcdetails.txt file by using the Findstr command, and then view the details in the Sfcdetails.txt. To do this, follow these steps:

    1. Open an elevated command prompt as described in the previous step 1.
    2. At the command prompt, type the following command, and then press ENTER:
      findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

      Note The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool.

    3. Open the Sfcdetails.txt file from your desktop.
    4. The Sfcdetails.txt file uses the following format:

      Date/Time SFC detail

      The following sample log file contains an entry for a file that could not be repaired:

      2007-01-12 12:10:42, Info                  CSI    00000008 [SR] Cannot 
      repair member file [l:34{17}]"Accessibility.dll" of Accessibility, Version = 
      6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, 
      VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type 
      neutral, TypeName neutral, PublicKey neutral in the store, file is missing
    How to manually replace a corrupted system file with a known good copy of the file

    After you determine which system file was corrupted and could not be repaired through the detail information in the Sfcdetails.txt file, find where the corrupted file located, and then manually replace the corrupted file with a known good copy of the file. To do this, follow these steps:

    Note You may be able to get a known good copy of the system file from another computer that is running the same version of Windows with your computer. You may perform a System File Checker process on that computer to make sure the system file that you intend to copy is a good copy.

    1. Take administrative ownership of the corrupted system file. To do this, at an elevated command prompt, copy and then paste (or type) the following command, and then press ENTER:

      takeown /f Path_And_File_Name

      Note The Path_And_File_Name placeholder represents the path and the file name of the corrupted file. For example, type takeown /f C:\windows\system32\jscript.dll. A screenshot for this step.

    2. Grant administrators full access to the corrupted system file. To do this, copy and paste (or type) the following command, and then press ENTER:

      icacls Path_And_File_Name /GRANT ADMINISTRATORS:F

      Note The Path_And_File_Name placeholder represents the path and the file name of the corrupted file. For example, type icacls C:\windows\system32\jscript.dll /grant administrators:F.A screenshot for this step.

    3. Replace the corrupted system file with a known good copy of the file. To do this, copy and paste (or type) the following command, and then press ENTER:

      Copy Source_File Destination

      Note The Source_File placeholder represents the path and file name of the known good copy of the file on your computer, and theDestination placeholder represents the path and file name of the corrupted file. For example, type copy E:\temp\jscript.dll C:\windows\system32\jscript.dll.


  • How to change the Volume Licensing product key on a computer that is running Windows XP Service Pack 1 and later versions of Windows XP

    http://support.microsoft.com/en-us/kb/328874

    Prerequisites

    You must have a valid product key before you can use the information in this article. To obtain a valid product key, click the following link to contact the Microsoft Volume Licensing Service Center:

    Steps to change the volume licensing product key

    This article describes two methods for how to change the Windows XP product key after a Volume Licensing installation to resolve the issue. One method uses the Windows Activation Wizard graphical user interface (GUI) and the other method uses a Windows Management Instrumentation (WMI) script. The Activation Wizard method is easier. However, if you must change the product key for multiple computers, the script method is more suitable.

    Method 1: Use the Activation Wizard

    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

    322756 How to back up and restore the registry in Windows

    If you only have a few volume licensing product keys to change, you can use the Activation Wizard.

    Note We recommend that you run System Restore to create a new restore point before you follow these steps.

    Deactivate Windows
    1. Click Start, and then click Run.
    2. In the Open box, type regedit, and then click OK.
    3. In the navigation pane, locate and then click the following registry key:

      HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\Current Version\WPAEvents

    4. In the topic pane, right-click OOBETimer, and then click Modify.
    5. Change at least one digit of this value to deactivate Windows.
    Reactivate Windows and add new product key
    1. Click Start, and then click Run.
    2. In the Open box, type the following command, and then click OK.

      %systemroot%\system32\oobe\msoobe.exe /a

    3. Click Yes, I want to telephone a customer service representative to activate Windows, and then click Next.
    4. Click Change Product key.
    5. Type the new product key in the New key boxes, and then click Update.

      If you are returned to the previous window, click Remind me later, and then restart the computer.

    6. Repeat steps 1 and 2 to verify that Windows is activated. You receive the following message:

      Windows is already activated. Click OK to exit.

    7. Click OK.
    8. Install Windows XP Service Pack 1a or a later version of Windows XP.

    If you cannot restart Windows after you install Windows XP SP1 or a later version of Windows XP, try the following steps:

    1. Restart your computer and start pressing F8 until you see the Windows Advanced Options menu.
    2. Select Last Known Good Configuration from the menu and press ENTER. This option starts Windows by using a previous good configuration.
    3. Repeat steps 1 through 8 under “Reactivate Windows and add new product key.”

    If you can install SP1 or a later version of Windows XP and you can restart Windows, you have resolved the issue. If the issue has not been resolved, try method 2 or see the “Next Steps” section for more troubleshooting resources.

    Method 2: Use a script

    If you must change the product key for multiple computers, we recommend this method. You can create a WMI script that changes the volume licensing product key, and then deploy this script in a startup script.

    The sample ChangeVLKey2600.vbs script and the sample ChangeVLKeySP1 script that are described in this section use the new volume licensing key that you want to enter as a single argument. It is in a five-part alphanumeric form.

    We recommend that you use the ChangeVLKey2600.vbs script on Windows XP-based computers that are not running Windows XP SP1 and later versions of Windows XP and that you use the ChangeVLKeySP1.vbs script on Windows XP-based computers that are running Windows XP SP1 and later versions of Windows XP. These scripts perform the following functions:

    • They remove the hyphen characters (-) from the five-part alphanumeric product key.
    • They create an instance of the win32_WindowsProductActivation class.
    • They call the SetProductKey method with the new volume licensing product key.

    You can create a batch file or a cmd file that uses either of the following sample scripts, together with the new product key as an argument. You can deploy it as part of a startup script or run it from the command line to change the product key on a single computer.

    Examples

    For more information about how to script the product key, visit the following Microsoft Web site:

    ChangeVLKeySP1.vbs
    ' 
    ' WMI Script - ChangeVLKey.vbs
    '
    ' This script changes the product key on the computer
    '
    '***************************************************************************
    
    ON ERROR RESUME NEXT
    
    if Wscript.arguments.count<1 then
       Wscript.echo "Script can't run without VolumeProductKey argument"
       Wscript.echo "Correct usage: Cscript ChangeVLKey.vbs ABCDE-FGHIJ-KLMNO-PRSTU-WYQZX"
       Wscript.quit
    end if
    
    Dim VOL_PROD_KEY
    VOL_PROD_KEY = Wscript.arguments.Item(0)
    VOL_PROD_KEY = Replace(VOL_PROD_KEY,"-","") 'remove hyphens if any
    
    for each Obj in GetObject("winmgmts:{impersonationLevel=impersonate}").InstancesOf ("win32_WindowsProductActivation")
    
       result = Obj.SetProductKey (VOL_PROD_KEY)
    
       if err <> 0 then
          WScript.Echo Err.Description, "0x" & Hex(Err.Number)
          Err.Clear
       end if
    
    Next
    ChangeVLKey2600.vbs
    ' 
    ' WMI Script - ChangeVLKey.vbs
    '
    ' This script changes the product key on the computer
    '
    '***************************************************************************
    
    ON ERROR RESUME NEXT
    
    if Wscript.arguments.count<1 then
       Wscript.echo "Script can't run without VolumeProductKey argument"
       Wscript.echo "Correct usage: Cscript ChangeVLKey.vbs ABCDE-FGHIJ-KLMNO-PRSTU-WYQZX"
       Wscript.quit
    end if
    
    Dim VOL_PROD_KEY
    VOL_PROD_KEY = Wscript.arguments.Item(0)
    VOL_PROD_KEY = Replace(VOL_PROD_KEY,"-","") 'remove hyphens if any
    Dim WshShell
    Set WshShell = WScript.CreateObject("WScript.Shell")
    WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents\OOBETimer" 'delete OOBETimer registry value
    for each Obj in GetObject("winmgmts:{impersonationLevel=impersonate}").InstancesOf ("win32_WindowsProductActivation")
    
       result = Obj.SetProductKey (VOL_PROD_KEY)
    
       if err <> 0 then
          WScript.Echo Err.Description, "0x" & Hex(Err.Number)
          Err.Clear
       end if
    
    Next

    The following example shows how to use the ChangeVLKeySP1.vbs script from a command line:

    1. Click Start, and then click Run.
    2. In the Open box, type the following command, where AB123-123AB-AB123-123AB-AB123 is the new product key that you want to use, and then click OK:

      c:\changevlkeysp1.vbs ab123-123ab-ab123-123ab-ab123


  • How to import .nk2 files into Outlook 2013

    http://support.microsoft.com/kb/2806550

    When you start Microsoft Outlook 2013 for the first time, your nickname cache (stored in the profilename.nk2 file) is imported into a hidden message in your default message store. 
    Note profilename is the name of your Outlook profile.

    For example, if you are using a Microsoft Exchange account, the nickname cache is imported into a hidden message in the Exchange mailbox.

    Note Outlook 2007 and earlier versions store the nickname cache .nk2 file in the following folder.

    • Windows XP
      Drive:\Documents and Settings\Username\Application Data\Microsoft\Outlook
    • Windows Vista and later versions
      Drive:\Users\Username\AppData\Roaming\Microsoft\Outlook

    After the nickname cache is imported, the profilename.nk2 file is renamed to profilename.nk2.old. On the next start of Outlook, your nickname cache is not imported. Outlook 2013 does not use the .nk2 file for maintaining your nickname cache. All updates to your nickname cache in Outlook 2013 are made to the hidden message in your default message store.

    Note If you have multiple Outlook profiles, the nickname cache from each profile is merged into your new Outlook 2013 nickname cache on the first start of Outlook 2013 by using that profile. Therefore, you may find more than one .nk2 file renamed to .nk2.old.

    However, there may be situations where you have to import a nickname cache file after this first-run nickname cache import process has finished. For example, a colleague wants to share their nickname cache with you and you want to update your existing nickname cache with your colleague’s data.

    This article discusses how to import .nk2 files into Outlook 2013.

     

    To import .nk2 files into Outlook 2013, follow these steps:

    1. Make sure that the .nk2 file is in the following folder:

      %appdata%\Microsoft\Outlook

      Note The .nk2 file must have the same name as your current Outlook 2013 profile. By default, the profile name is “Outlook.” To check the profile name, follow these steps:

      1. Click Start, and then click Control Panel.
      2. Double-click Mail.
      3. In the Mail Setup dialog box, click Show Profiles.
    2. Click Start, and then click Run.
    3. In the Open box, type outlook.exe /importnk2, and then click OK. This should import the .nk2 file into the Outlook 2013 profile.

      Note After you import the .nk2 file, the contents of the file are merged into the existing nickname cache that is currently stored in your mailbox.

    Note The .nk2 file is renamed with a .old file name extension on the first start of Outlook 2013. Therefore, if you try to re-import the .nk2 file, remove the .old file name extension.


  • How to configure the size limit for both (.pst) and (.ost) files in Outlook

    http://support.microsoft.com/kb/832925/en-us

    Microsoft Outlook 2013, Microsoft Outlook 2010, Microsoft Office Outlook 2007, and Microsoft Office Outlook 2003 support American National Standards Institute (ANSI) and UNICODE personal folders (.pst) and offline folder (.ost) files. This article describes how to use the following four registry entries to limit the size of both the .pst and the .ost files:

    • The MaxFileSize registry entry
    • The WarnFileSize registry entry
    • The MaxLargeFileSize registry entry
    • The WarnLargeFileSize registry entry

    Note The WarnLargeFileSize and WarnFileSize registry entries do not enable Outlook to warn you before the file size limit is reached.

    The MaxFileSize registry entry

    The MaxFileSize registry entry determines the absolute maximum size that both the .pst and the .ost files can grow to. After this maximum size is reached, Outlook does not permit the size of the file to grow beyond this size.

    The WarnFileSize registry entry

    The WarnFileSize registry entry determines the maximum data that both the .pst and the .ost files can have. After this maximum data is reached, neither the .pst nor the .ost files are permitted to add any more data. However, the size of the physical file may still increase because of internal processes.

    In the following table, the MaxLargeFileSize registry entry and the WarnLargeFileSize registry entry refer to a UNICODE formatted (new Large format) file, and the MaxFileSize registry entry and the WarnFileSize registry entry refer to an ANSI formatted (an earlier Microsoft Outlook format) file. The UNICODE values are set in megabyte (MB) increments, while the ANSI values are set in byte increments.

    Outlook 2013 and Outlook 2010

    Name Type Valid Data Range Default
    MaxLargeFileSize REG_DWORD 0x00000001 – 0x0000C800 0x0000C800 51,200 (50 GB)
    WarnLargeFileSize REG_DWORD 0x00000000 – 0x0000BE00 0x0000BE00 48,640 (47.5 GB)
    MaxFileSize REG_DWORD 0x001F4400 – 0x7C004400 0x7BB04400 2,075,149,312 (1.933 GB)
    WarnFileSize REG_DWORD 0x00042400 – 0x7C004400 0x74404400 1,950,368,768 (1.816 GB)

    Outlook 2007 and Outlook 2003

    Name Type Valid Data Range Default
    MaxLargeFileSize REG_DWORD 0x00000001 – 0x0000C800 0x00005000 20,480 (20 GB)
    WarnLargeFileSize REG_DWORD 0x00000000 – 0x0000BE00 0x00004C00 19,456 (19 GB)
    MaxFileSize REG_DWORD 0x001F4400 – 0x7C004400 0x7BB04400 2,075,149,312 (1.933 GB)
    WarnFileSize REG_DWORD 0x00042400 – 0x7C004400 0x74404400 1,950,368,768 (1.816 GB)
    Expand this table
    Office Version The policy location for the registry entries is located in the following path in Registry Editor The user preference location for the registry entries is located in the following path in Registry Editor
    Outlook 2013 HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Outlook\PST HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\PST
    Outlook 2010 HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\PST HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\PST
    Outlook 2007 HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook\PST HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\PST
    Outlook 2003 HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Outlook\PST HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\PST

    Collapse imageMore information

    Follow these steps to configure the size limit for both the .pst and the .ost files.

    Note The settings that are discussed in this article apply to both .ost and .pst files. If you modify these registry values, this can affect .ost files that are used with Cached Exchange Mode, with AutoArchive, and with .pst. files. If Outlook is configured to download shared folders, the contents of shared folders are stored in the local Offline Outlook Data (.ost) file. If the shared folders contain many items or large attachments, the size of the .ost file may grow significantly. Additionally, Outlook 2013 introduced support for Site Mailboxes. If an Outlook 2013 client is working in a Microsoft Exchange Server 2013/Microsoft SharePoint 2013 environment and is granted permission to a site mailbox, the site mailbox is automatically added to the Outlook 2013 profile. If Download Shared Folders is enabled, the site mailbox contents are synchronized to the local .ost file. This can result in the .ost file exceeding the set limit. For more information about the Download Shared Folders setting in Outlook, click the following article number to view the article in the Microsoft Knowledge Base:

    982697 By default, shared mail folders are downloaded in Cached mode in Outlook 2010 and Outlook 2013

    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

    322756 How to back up and restore the registry in Windows

    1. Click Start, and then click Run.
    2. In the Open box, type regedit, and then click OK.
    3. In the left pane, expand My Computer, and then expand HKEY_CURRENT_USER.
    4. Expand Software, and then expand Policies.
    5. Expand Microsoft, and then expand Office.
    6. Expand 11.0 for Outlook 2003, 12.0 for Outlook 2007, or 14.0 for Outlook 2010, or 15.0 for Outlook 2013, and then expand Outlook.
    7. Click PST, and then right-click MaxFileSize in the right pane.
    8. Click Modify, and then type the value in the Value data box.
    9. Click OK.
    10. Right-click WarnFileSize, and repeat steps 8 through 9.
    11. Right-click MaxLargeFileSize, and repeat steps 8 through 9.
    12. Right-click WarnLargeFileSize, and repeat steps 8 through 9.

    Note You may have to create the registry values if they do not exist. If the registry values do not exist, follow these steps to create them.

    1. Click Start, click Run, type Regedit, and then click OK.
    2. In the left pane, expand following registry key:

      For Outlook 2013

      HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Outlook

      For Outlook 2010

      HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook

      For Outlook 2007

      HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook

      For Outlook 2003

      HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Outlook

    3. Right click Outlook, point to New, and then click Key. (The screen shot for this step is listed below).

      Screen shot for step 3

    4. Type PST, and then press ENTER. (The screen shot for this step is listed below).

      Screen shot for step 4

    5. Right click PST, point to New, and then click DWORD value. (The screen shot for this step is listed below).

      Screen shot for step 5

    6. Type MaxFileSize, and then press ENTER twice. (The screen shot for this step is listed below).

      Screen shot for step 6

    7. In the Edit DWORD Value window, choose Decimal and type the value in the Value data box, and then click OK.
      Note 1GB=1*1024*1024*1024byte; 1MB=1*1024*1024byte; 1KB=1*1024byte, the example below is for 1GB. (The screen shot for this step is listed below).

      Screen shot for step 7

    8. Repeat steps 3 through 7 to create another DWORD WarnFileSize.
    9. Repeat steps 3 through 7 to create another DWORD MaxLargeFileSize.
    10. Repeat steps 3 through 7 to create another DWORD WarnLargeFileSize, and then close the registry.

      Note For mass deployment of these registry keys on end-user machines, the ORK tool can be used.

    To automate the registry creation on end-user machines, use ORK for deployment scenarios.
    It is recommended that the values between the MaxFileSize registry entry and the WarnFileSize registry entry, and the values between the MaxLargeFileSize registry entry and the WarnLargeFileSize registry entry be at least 5 percent (%) so that internal processes are not hindered from continuing.

    If the value of the MaxFileSize registry entry ever exceeds the ANSI 2 gigabyte (GB) limit on either the .pst or the .ost files, the value will be ignored to limit the size to 2 GB to prevent corruption. The default value for the WarnFileSizeregistry registry entry is calculated to be 95% of the MaxFileSize registry entry for a UNICODE file, and it remains at 1,950,368,768 bytes for small ANSI files.

    Note You can set the UNICODE limits beyond the values that are listed in the table. However, we do not recommend doing this because performance can decrease.

    If .ost files or .pst files reach the limit that is specified in the WarnFileSize or the WarnLargeFileSize registries, the compaction function is triggered to try to reduce the size of the file to a usable level. When the WarnFileSize or the WarnLargeFileSize limit is reached, e-mail messages cannot be sent (provided that sent e-mail messages are stored in the Sent Items folder), and items cannot be copied or moved within the file. If the file is an archive .pst file that is used for AutoArchive, the AutoArchive operation will fail. However, e-mail messages can be deleted or archived from a .pst or from an .ost file that is currently being used as the default delivery location.

    The following are some of the errors that may occur when files reach the maximums specified in the registries:

    • When you try to move items to a .pst or an .ost file that has reach the limit, you receive the following error message:

      Can’t move the items. The file <path>\<filename>.pst has reached its maximum size. To reduce the amount of data in this file, select some items that you no longer need, and then permanently delete them.

    • When e-mail messages are delivered to a .pst or an .ost file that are using Cached Exchange Mode, and the file has reached the limit, the Mailbox Cleanup wizard launches.

  • Virus:DOS/Rovnix.gen!A | Bootrec.exe tool

    Virus:DOS/Rovnix.gen!A

    Microsoft security software detects and removes this threat.

    This virus can make your PC crash unexpectedly. If you can reboot your PC after the crash, you should run a full antivirus scan.

    It can be distributed in similar ways to other malware, for example, by exploiting vulnerabilities, or installed by other malware, such as TrojanDropper:Win32/Rovnix.H.

    Find out ways that malware can get on your PC.

    ——————————————————————————–
    What to do now
    Use the following free Microsoft software to detect and remove this threat:

    •Windows Defender for Windows 8.1, or Microsoft Security Essentials for Windows 7 and Windows Vista
    •Microsoft Safety Scanner
    You should also run a full scan. A full scan might find other, hidden malware.

    Get more help
    To restore your PC, you might need to download and run Windows Defender Offline. See our advanced troubleshooting page for more help.

    You can also ask for help from other PC users at the Microsoft virus and malware community. If you’re using Windows XP, see our Windows XP end of support page.

    Run the Bootrec.exe tool
    To completely remove this threat you might need to run the Bootrec.exe tool using your Windows installation CD.

    For Windows 8:

    1.Put your Windows 8 media in the DVD drive and restart your PC.
    2.Select a language, time and currency, and keyboard or input method, and then click Next.
    3.Click Repair your computer.
    4.Click Troubleshoot, then Advanced options.
    5.Click Command Prompt and then type Bootrec /FixBoot and then press Enter.
    6.Type Exit and the press Enter.
    7.At the Choose an Option screen click Continue.
    8.Remove the Windows 8 CD from your DVD drive and restart your PC.
    For Windows 7:

    1.Put your Windows 7 media in the DVD drive and restart your PC
    2.Press any key when you are prompted.
    3.Select a language, time and currency, and keyboard or input method, and then click Next.
    4.Click Repair your computer.
    5.Select the operating system that you want to repair, and then click Next.
    6.In the SystemRecovery Options dialog box, click Command Prompt.
    7.Type Bootrec.exe /fixboot, and then press Enter.
    8.Remove the Windows 7 CD from your DVD drive and restart your PC.


  • How to fix a corrupt user profile in Windows: The User Profile Service failed the logon

    http://www.pcadvisor.co.uk/how-to/windows/3495216/how-fix-corrupt-user-profile-in-windows-7/

    Plus: How to enable the hidden Administrator account

    By Marc Norris | PC Advisor | 19 May 14

    The User Profile Service failed the logon

     Corrupt user profiles are a frustratingly common problem withWindows and there are various problems and solutions depending on the exact error message you receive. Here we show you how to recover from a corrupt user profile by either fixing the problem or creating a new account and transferring your user data across to the new profile.

    See also: Windows 8.1 review

    When you type your password and press Enter, you will typically see the error message “The User Profile Service failed the logon” and “The user profile cannot be loaded”, and you’ll be returned to the logon screen.

    WARNING: Some people have lost files by using Method 1 below, so create a backup of your hard disk, or just files you cannot afford to lose before trying anything which involves editing the Windows Registry. There are various programs which will allow you to make a copy of your entire disk, but you will need a second disk with sufficient capacity, and may even need a second PC or laptop in order to copy the disk (if you can’t boot into Windows). You should also make a backup of the Registry itself from Safe Mode before you start. These instructions are provided as a last resort, and we recommend you try Method 2 – below – before trying Method 1.

    Method 1: Fix a corrupt profile

    Microsoft says that a user profile can become corrupted if your antivirus software is scanningyour PC while you try to log on, but it could also be caused by other things.

    A quick fix can be to restart your PC, but if this doesn’t work you’ll need to restart again and boot into Safe mode. Do this by pressing F8 before you see the Windows loading screen and choosing Safe Mode from the menu that appears.

    Safe Mode logs you into the built-in Windows administrator account, but you might find that some options don’t work.

    Step 1. To fix the user profile, click Start and type regedit into the search box and press Enter.

    Step 2. Registry Editor will launch and you need to navigate to the following key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    Step 3. Click each S-1-5 folder and double-click the ProfileImagePath entry to find out which user account it relates to. (If your folder name ends with .bak or .ba follow Microsoft’s instructions to rename them.)

    If you can’t see any file extensions at all, follow our instructions to display Windows file extensions.

    Fix corrupt user profile Windows

    Step 4. Once you have located the folder for the corrupt profile (and it doesn’t have a .bak ending), double-click RefCount and change the Value data to 0 and click Ok.

    Fix corrupt user profile Windows

    Step 5. Now double-click on State and make sure the Value data is again 0 and click Ok.

    Fix corrupt user profile Windows

    Step 6. Close regedit and restart your PC. You should now be able to log into your account.

    Method 2. Create a new user profile

    If you have a second account on your PC which you can log in to, you may be able to use this account to follow the steps below to create a new user account.

    However, if there is no other account, boot into Safe Mode (as described above) and try to follow the steps. If that still doesn’t work, you need to enable the hidden admin account. To do this, type cmd in the search box and then right-click on Command Prompt in the list of results and choose Run as administrator.

    Now type the following at the prompt:
    net user administrator /active:yes

    The response should be: The command completed successfully. Now reboot your PC and you should see an Administrator account as well as your corrupt account. Log into the admin account (there’s no password) and follow the steps below:

    Step 1. Open Control Panel and click User Accounts and Family Safety (or similar). Click on User Accounts.

    How to fix a corrupt user profile - Step 1

    Step 2. Click Manage another account and type in the password (if prompted).

    Step 3. Click Create a new account and type the name. This must be different from the account which is corrupt, but you can rename the account later on if you want to have the same name as before.

    How to fix a corrupt user profile - Step 3

     Step 4. Restart your PC.

    How to fix a corrupt user profile - Step 4

    COPY USER FILES TO THE NEW PROFILE

    Step 5. In order to transfer files properly, it’s best to log in as Administrator or Guest rather than the new profile you just created, so enable one of these accounts if you haven’t already done so.

    How to fix a corrupt user profile - Step 5

    Step 6. Navigate to the corrupt user account by clicking Start, Computer and then double-clicking on the hard drive on which Windows is installed – usually c: – and then double-clicking on the Users folder. Find the folder containing your old user account and double-click it, then double-click My Documents.

    How to fix a corrupt user profile - Step 6

     Step 7. It’s best to copy across the contents of sub-folders separately, and this gives you a chance to have a clear out as well. If you do want to copy the entire contents in one go, enable hidden files and folders and then make sure you DON’T copy across the following files:

    Ntuser.dat
    Ntuser.dat.log
    Ntuser.ini

    To make these files visible, click the Tools menu (press Alt if you can’t see it), click the View tab and click Show hidden files, folders and drives.

    How to fix a corrupt user profile - Step 7

    Beware that any email stored locally may need to be copied separately using instructions specific to your email program. Don’t delete the corrupt user profile until you’re sure you have all the files you need from it.

    Step 8. When all the files are copied across to the newly created user profile (you’ll find it in the same c:\Users folder as the corrupt profile), restart your computer and log onto the new profile.

    How to fix a corrupt user profile - Step 8