So, let’s say you’re in a situation where you don’t have roaming profiles or you just got a new PC and don’t feel like recreating all your Outlook settings. There is a simple way of doing this.
NOTE: You can also use these steps to just simply backup your Microsoft Outlook profile and settings.
On the original computer/user profile do the following:
- Close Outlook (if open)
- Click on Start and then Run and enter ‘Regedit’ and press enter.
- Navigate through the registry to:
‘HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles’
- Click on File
- Click on Export
- Save the .REG file to a external drive or a network path (whichever you prefer).
On the new computer/user profile do the following:
- Open the the location where you saved the .REG file from the other computer
- Double click on the .REG file and import the registry settings
- Start Outlook to confirm everything is OK.
If you feel like something was not imported incorrectly or there was an issue simply delete the new profile created in the registry or open up ‘Mail’ in the ‘Windows Control Panel’.
Note: If you have multiple profiles on the original PC they will all transfer. You can delete the rest individually by going to Mail in the Control Panel.
Recreating a corrupt Windows 7 profile isn’t as simple as some may think. There are a few simple steps you need to take to do so.
- Restart your PC to release the locks on your profiles.
- Log on with another administrative account.
- Rename or Delete the user’s profile folder (C:\Users\%username%\)
- Delete any Temp Profiles that may have been created during your first attempt at recreating the profile. (C:\Users\TEMP\).
- Delete or Rename the registry key matching your SID from
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList”. Check the value “ProfileImagePath” to make sure you pick your own profile. I like to add a ‘.bak’ to the key in the registry.
- Restart and now log in with the account you were trying to recreate.
I recently came across a machine where .NET Framework 3.5 wasn’t functioning correctly. It was needed as a prerequisite and the application was not recognizing it even though it was enabled in the “Turn Windows Features on and off” (Search for this on the Windows Start Menu).
If uninstalling and installing .NET on Vista does not work you can run a command to scan and repair system files. Since .NET 3.5 is part of Windows 7 you can’t easily uninstall it. Try this command out and it should help if you actually have corrupt system files.
- Open a command prompt (CMD) window and make sure you ‘Run As Administrator’. (Search for CMD in your Windows 7 Start Menu and then right click CMD.EXE and select ‘Run As Administrator’).
- Enter the following command and press enter: sfc /scannow
This can take a while but let it run. This will scan all protected system files and replace incorrect versions with correct Microsoft versions. Once it has completed reboot your machine and try again.
If any errors are reported that SFC was unable to fix, there are steps in this knowledge base article that explain how to locate and attempt to fix the errors
Open the ‘Start‘ menu and type ‘CMD‘ in the search bar. Right click on ‘CMD‘ and select ‘Run as Administrator‘
When the command prompt opens up type the command ‘printui /s /t2‘.
Select the Printer you would like to Remove and click on ‘Remove..’. Remember to select ‘Remove driver and driver package’.
If you have difficulty removing the driver and package you can stop and start the ‘Print Spooler’ service. You can do this by searching for ‘service.msc’ in your Windows 7 start menu (Remember to Run as Administrator). Find the service named ‘Print Spooler’. Right click and Stop the service and then Start the service. After you have done that you can try removing the Driver / Driver Package again.
I came across this problem recently at my job. We recently migrated from Windows Server 2003 to Windows Server 2008 and during this process we were also upgrading our desktops to Windows 7.
We started seeing this MSI error randomly once we moved a large majority of user ‘home drive’ shares to our new Windows 2008 Server. From my understanding, MSI files verify free space of the users “Home” directory (My Pictures, My Music, etc). Since we use folder redirection it looks to the full UNC path which is in the registry under the following path:
Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
If you change all the values pointing from the UNC path to ‘%userprofile%\Path’ the error will go away but this needs to be done each time the user logs on and off. But, that will only happen if you use folder redirection.
After doing some research and testing I realized that Windows 7 + Windows Server 2008 requires a specific security change to the folder or else this error will constantly occur. Under Advanceed > Change Permissions for “Authenticated Users” or “Domain Users’ (We used Auth. Users) we needed to add “Read Attributes” and apply it to “This folder only”.
The error should go away after you make this change. Making this change WILL NOT allow for anyone to see the given folder. It is simply an attribute. We tested and confirmed this in our environment.
This is a pretty random issue we came across at my job but apparently this can happy with Windows 7. Users were randomly losing connection to their network share. It would tell them that the location is unavailable. We realized that the Offline files service in Windows 7 was running and for some reason it was causing their drive to go offline.
There is a simple solution for this. First, turn off and disable the ‘Offline Files’ service if you don’t plan on using it. Also, add the following registry key:
Create Key Name: FormatDatabase
Note: You don’t need to disable the service but there is no reason it should be running for desktop computers.
Warning: All cache files are deleted and unsynchronized data is lost. (applies to laptops that sync)
I came across this error the other day. I’ve installed SQL 2008 through 2012 without any real issues. Recently, I was trying to run the installer again so that I can add some features. I kept getting this message. It would even come up when I would try to do a change from Add/Remote Programs. I figured out the fix and it was pretty simple.
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\Resources\1033
Make sure you overwrite the file.