Most Windows 8 users might not face this issue, but the smarties will surely have faced this issue. I too was one among them until a few days back, but I too have managed to upgrade my OS from Windows 8 to Windows 8.1. This error appears, each time you try to download and upgrade from the Windows store. The download goes fine but when it enters the installation stage, the doomed message appears. Most users love to tweak their brand new laptops a little. This includes moving the Users folder to the D or E drive (the second partition). This is being done to save space for the OS partition, commonly known as the C partition or the C Drive. Some users even install programs (Games or bigger applications) on their secondary partition so as to save space. Either ways, this affects the upgrade to Windows 8.1 and you are all but lost.
After having gone through a lot of forums and sitting for days in front of my laptop to find an answer to this problem, I had the final laugh. I too had redirected all my Users folder and also had installed a game on the D drive of my laptop. At the time of installation I encountered this error message and tried reversing all the changes that I had made. That didn’t help. Before we get into all this, please note that my secondary partition was D but that need not be the case for all. The letters could change for different users. Please make a note of the letter on your secondary partitionThe steps that I followed are as follows:
- On your PC or laptop, type in “regedit” (without quotes). This opens the regedit window. Go to HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/ProfileList/ProfilesDirectory and change the value of it back to “%SystemDrive%\Users” (without quotes again). Close this window.
- Go to control panel and click User Accounts. Click on “Manage Another Account”. In this windows, click on the option “Add a new user in PC Settings”.
- This will take us to another window asking us to “Add an account”.
- Click on it but please make sure to click on the bottom most option, “Sign in without a Microsoft Account (not recommended)”. It says not recommended but at this stage I feel it is better to go without one. Click on the option “Local Account”. Create a username of your choice with password and click Finish.
- Once the account is created, go back to User Accounts in Control Panel and click “Manage Accounts”. Click the new account that was just created and click on “Change the Account type”. Change it to Administrator.
- Sign out from the current user account.
- Sign in with the newly created user.
- The new account will created in C:\Users.
- In the new account, type in “cmd” (without quotes) and right click on it and click “Run as Administrator”. We now need to make a Junction from the C: profile folders to the D: profile folders.This is done by running the command mklink /J C:\Users\Username D:\Users\Username
- Once this is done, you are returned with a success status.
- Open “regedit” again as described in the first step and go to HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/ProfileList/S-1-5-xx-xxxxxxxx-xxxxxxxxxxxxxx/ProfileImagePath. We need to change all the keys that point to D:\Users\Username to C:\Users\Username.
- Once this is done, we need to check if we are able to log on to the old user account again.
- Log out of the old user account and log in back to the newly created user account.
- The steps above needs to be repeated for every account which has its profile folders on the D partition.
- If there are any pending updates, install them and restart the laptop or PC. The restart makes sure that all the Users that are current logged in are logged out and also to make sure that no user on D partition is logged in.
- After the restart log on to the new user account. Go to Windows Store, download and install the 8.1 update.
I did notice recently that after having installed and configured Exchange 2013 on Windows 2012 Standard, sucessfully, IE 10 starts acting weird each time I try to work on EAC (Exchange Admin Centre) using this browser.
From other other blogs and posts that have suggested different work arounds, I found downloading and installing the following security patch to be the best. You may either visit the Microsoft website and download the patch or waste no time and download it directly from here. I did not have any issues thereafter. However, you can still browse the EAC page from your laptop or PC with Windows 8 installed and use the IE 10 on it.
Cannot add 32 bit print drivers on Windows Server 2008 R2
This has been one of the most difficult issues that I have dealt with having been an administrator myself. Windows Server 2008 R2 is such a treat to have in one’s organization. But it starts to become a pain when you decide to make it your print server. Wait! Do not ditch your plans to upgrade you print server OS yet. There is a work around, a very simple one though. But this is being done in different ways according to how stringent are your company’s security policies.
The scenario that I’m talking about here is when each time you try to add a 32 bit driver to your server, the server tries adding the printer driver and in the final stage it comes with a pop up window asking for “i386” files.
It certainly is looking for ntprint.inf files without which it cannot install the 32 bit drivers. All the happiness that I had of installing this OS had all gone down the drain, the moment I saw this pop up. I encountered this issue when we were trying to add the printer driver for a Xerox WorkCentre 5890 machine that we had in our work premises (I’m sure that you don’t encounter such issues with all the printer drivers).
I had gone through a lot of posts which had suggested that the 32 bit driver be added to a 32 bit workstation in the network and then have it pushed to the server. But this scenario was not going to work in my case because our organization had group policies enabled whereby sharing or pushing files from any workstation to another workstation or server was just out of the question. So I really had to look for a workaround.
That’s when I read somewhere in a Microsoft Technet blog where a lad had written a very simple method when a dozen of others had talked about a lot of other tricks and techniques. The trick is a simple one. On one of the 32 bit Windows 7 or Windows Vista workstations that you have in your network, copy the folder starting with the name “ntprint.inf_xxxxx” from the location C:\Windows\system32\DriverStore\FileRepository\ntptint.inf_xxxxx to any location of the server (Desktop of the server would be fine too) where you are trying to isntall the 32 bit printer driver. Once done, run the “Add Driver” again. The moment it asks for the i386 thingy, just click on “Browse” and point it to the location on the desktop where the folder was copied.
Alternatively if your company security policies allow you to share a folder from a workstation, you needn’t even copy these files to the server. You can just copy them to a different location on the same workstation and share it there. Go back to the server and reach the point where it asks for the ntprint.inf files and point it to this shared location. I haven’t tried this since our group policies never entertained such tricks.
There you go!! It installs cleanly without any hassle.
After having found this work around I had taken up a project whereby every branch server in our network had to be upgraded to Windows Server 2008 R2 and boy didn’t I have a great time? Yes, I did. Indeed!!
Applies to Windows 7 / Windows 8
A reboot would ideally get you through this. A quick option would be to kill explorer.exe and reinstate it
- Open Task Manager
- From the Processes Tab; right-click on explorer.exe and select End Process
- Your task bar would immediately disappear
- From the File Menu, of your Task Manager; click New Task
- Type in explorer.exe and click ok
- Your task bar should return and you can resume uninstallation of your program
I did not realize that this was possible until a colleague told me about it
There is a built VB Script within Windows 7 which provides this feature
Open Command Prompt
- slmgr.vbs -ipk <type your product key here>
- To activate windows type – slmgr.vbs –ato
- And you are done !
When trying to use Compressed (zipped) Folder in Windows 7 you get the error message
“includes characters that cannot be used in a compressed folder”
First thing to do would be to check for any unrecognized characters in file / folder names of the files you wish to compress. You can rename them to resolve this issue.
But if this is not an unrecognized character; but instead a language different from you PC Default; there are two things you can do
- If renaming the file name or folder is ok for you as well as the recipient who expects to recieve your compressed file; you can proceed with the same
- Or else; an easy option would to be use either WinRAR or 7-Zip to do the compress operation and restore all the characters in the file and folder names
- If you prefer using the default Compressed (zipped) Folder option; you would need to change the System Locale under Control Panel – Region and Languages – Administrative and add the required language. This is a far fetched exercise and not really recommended unless it is a very regular of you dealing with files or folder names that are non-english
If you Print Spooler stops regularly; you may find this error in the Event Viewer
Firstly; go to your Devices and Printers and remove all printers that you do not use or are error prone.
Secondly go to c:windowssystem32spoolPRINTERS and delete and files
Thirdly under registry; Run – Regdit