Archive for the ‘MS Windows’ Category

Error “WindowsUpdate_80244019” or “WindowsUpdate_dt000” during update your Windows.

The problem in majority of the cases is related to the wrong DNS loading. The problem itself very often happens when you are behind several routers (like one from internet connection vendor and one your WiFi router) and until you don’t flush your current DNS configuration you can try anything but you won’t be successful.
What’s really funny that’s so easy – just run the command prompt with admin rights, then run the following command:

ipconfig /flushdns

make a coffee and get back to the WU heaven 🙂
All other applications are able to deal with that – WU not. From my point of view this is a bug and I am just surprised it’s nowhere documented.

You could also register the DNS in command prompt with:

ipconfig /registerdns

and check your current DNS settings with:

ipconfig /displaydns

Hope this helps!


How to get and install the “Microsoft Office Picture Manager” in Office 2013 and above.

If you are using Microsoft Office 2013 you might have noticed that the new Office suites don’t come with “Microsoft Office Picture Manager” program. Picture Manager was an excellent and small program included in Office suite which used to help users in viewing, editing and managing pictures quickly and easily. It also used to provide a few advanced image editing features such as crop, auto correct, rotate, flip, red-eye removal, resize, etc.
Basically it was a nice piece of program to edit pictures but now its no longer included in Office suite. The reason looks very simple. This program was not updated since Office 2003 version and was looking out-of-date, that’s why Microsoft decided to discontinue its development.
But there are many Office users who are missing this nice little program and want to get it back in newer Office versions.
The idea behind adding this program back is very simple. You’ll use a previous Office suite setup and will customize it to install only Picture Manager program.
If you don’t have a previous Office version, you can use Microsoft SharePoint Designer (SPD) 2010 version to install Picture Manager (it’s absolutely free and doesn’t require any product key to activate). You can download it using following links:
Download Microsoft SharePoint Designer 2010 (32-bit)
Download Microsoft SharePoint Designer 2010 (64-bit)
By the way, it is interesting to note that Picture Manager is not a component of SharePoint Designer 2013.
Here you can find the detailed instructions with screenshots, etc.:
The short version is to run the installer, then choose “Customize” instead of “Install Now”, then deselect everything that’s not “Office Tools” => “Microsoft Office Picture Manager”.
That’s should be all 🙂

Categories: MS Windows, OS Tags: ,

Run .NET framework 1.1 apps and programs in Windows 8

Recently, I tried to run the .NET framework 1.1 supported application in Windows 8.1. As you may not know .NET Framework 1.1 is not supported on the Windows 8 or Windows Server 2012 operating system. In some cases, the .NET Framework 1.1 is specifically identified as required for an application to run. In those cases, you should contact your independent software vendor (ISV) to have the application upgraded to run on the .NET Framework 3.5 SP1 or later version.
But there are cases (very often) when the software version is old and you do not have the upgraded version of the software. In my case, I tried to install the package and got the following error message: “Setup cannot continue because this version of the .NET Framework is incompatible with a previously installed one“.

There are two methods to fix this issue.
Method 1 – install .NET Framework 3.5
For some users all those apps which need .NET Framework 1.1 to run can work properly with .NET framework 3.5. So, you can optionally download .NET 3.5 and install it but make sure you can turn off 4.0 framework and other versions if you have it apart from 3.5. So you have to turn off .NET 4.0 and leave on .NET 3.5 – in my case, it didn’t solve the issue.

Method 2 – manually install .NET Framework 1.1
Download Microsoft .NET Framework 1.1 redistributable package (dotnetfx.exe). Make sure the setup file is saved as dotnetfx.exe. Download Microsoft .NET Framework 1.1 Service Pack 1 (NDP1.1sp1-KB867460-X86.exe). Make sure that the file is renamed and saved as dotnetfxsp1.exe, so that the rest of the steps can be followed easily. Move both installation files into the same directory (for example c:\dotnet).
This method involves recompiling the .NET framework 1.1 and then installing .NET Framework 1.1 with slipstreamed/integrated SP1 by running netfx.msi which will created in the working folder after running the following commands (run command prompt in admin mode and run the following command one by one):

dotnetfx.exe /c:"msiexec.exe /a netfx.msi TARGETDIR=C:\DotNet"

after it is installed

dotnetfxsp1.exe /Xp:C:\DotNet\netfxsp.msp


msiexec.exe /a c:\DotNet\netfx.msi /p c:\DotNet\netfxsp.msp

I hope one of the above method will work for you to run any app or program. Make sure to restart your PC after following any of the above methods.

How to install ODBC driver for Oracle in Windows 7.

2014-07-28 22 comments

Installation of the ODBC driver in Windows 7 is quite simple but there are a few tricks better to know. Here is a step-by-step instruction how to install the ODBC driver.
First of all, you need to download proper files:
– here is the link for Instant Client Downloads for Microsoft Windows (32-bit), for ODBC, you need and files (Oracle version)
– here is the link for Instant Client Downloads for Microsoft Windows (x64), for ODBC, you need and files (Oracle version)

Which version to choose – 32-bit or 64-bit?
Well, I think the best way to answer this question is to describe my situation. I need to get data from Oracle to Excel. I have on my PC: Windows 7 – 64-bit version, 64-bit Oracle client already installed but MS Office in 32-bit version. So in my situation I had to choose 32-bit ODBC driver. Generally, you choose ODBC driver version based on tool version, that you use to get data from Oracle database.

Anyway, both downloaded files, you need to unzip to THE SAME folder (for example: c:\oracle\instant_client_11), then add the folder to the PATH environment variable:
Then add the TNS_ADMIN environment variable indicating the path to the tnsnames.ora file (in my PC it is c:\oracle\11.2.0\CLIENT\network\admin):
Next, open the command line (Run as administrator) and go to the folder where you unzip ODBC driver, in my case:

cd c:\oracle\instant_client_11

and then – still in cmd, install ODBC:


When successfully, you should get the following info:

Oracle ODBC Driver is installed successfully.

So, right now we can configure ODBC connection: choose Control Panel, then Administrative Tools, then Data Sources (ODBC), then System DNS and then Add, on the list, choose instant_client_11, then Finish and then in the configuration window… wait. You don’t have instant_client_11 on the list. That’s the problem I also had – ODBC driver didn’t appear in ODBC data source.
This is because you use 64-bit ODBC administration panel. If you install 32-bit ODBC driver, you’ll need to use 32-bit ODBC administration panel – run odbcad32.exe from c:\windows\SysWOW64.

So, on the list, choose instant_client_11, then Finish and then in the configuration window add proper data in the Data Source Name, Description, TNS service name (from tnsnames.ora) and User ID.
Then, you can test connection and when everything is correct, save the connection, close ODBC window and enjoy your Oracle data in MS Office tools 🙂

Running Windows PowerShell scripts.

Few notes before, I wrote about finding the HP product number of any of your HP servers using PowerShell. First time, when I tried to do this, I double-clicked a .PS1 file (.PS1 being the file extension for Windows PowerShell scripts), sat back, and waited for the magic to happen.
As it turned out, however, this is what happened:
Instead of running, my script opened up in Notepad. Interesting, but not exactly what I had in mind. Oh wait, I thinked, I got it: I probably have to run Windows PowerShell before I can run a Windows PowerShell script. OK, that makes sense. And so, with that in mind, I opened up Windows PowerShell and typed the path to the .PS1 file at the command prompt. Pressed ENTER and waited for the magic to happen.
As it turned out, however, this is what happens:
Why did I get weird error messages when I try to run a script? That’s easy. The security settings built into Windows PowerShell include something called the “execution policy” – the execution policy determines how (or if) PowerShell runs scripts. By default, PowerShell’s execution policy is set to Restricted – that means that scripts – including those you write yourself – won’t run. Period.
How to verify the settings for your execution policy? By typing the following at the PowerShell command prompt and then pressing ENTER:


Now, admittedly, this might seem a bit severe. After all, what’s the point of having a scripting environment if you can’t even run scripts with it? But that’s OK. If you don’t like the default execution policy (and you probably won’t) then just go ahead and change it. For example, suppose you want to configure PowerShell to run – without question – any scripts that you write yourself, but to run scripts downloaded from the Internet only if those scripts have been signed by a trusted publisher. In that case, use this command to set your execution policy to RemoteSigned:

Set-ExecutionPolicy RemoteSigned

Alternatively, you can set the execution policy to AllSigned (all scripts, including those you write yourself, must be signed by a trusted publisher) or Unrestricted (all scripts will run, regardless of where they come from and whether or not they’ve been signed).
After I changed execution policy settings it’s possible to run scripts. However, there is a little trick that might run you into problems. For example, suppose you change directories from your Windows PowerShell home directory to C:\scripts (something you can do by typing cd C:\scripts). As it turns out, the C:\scripts folder contains a script named script.ps1. With that in mind I typed the script name, pressed ENTER and waited for the magic to happen.
As it turned out, however, this is what happens:
I know what you’re thinking: didn’t we just change the execution policy? Yes, we did. However, this has nothing to do with the execution policy. Instead, it has to do with the way that PowerShell handles file paths. In general, you need to type the complete file path in order to run a script. That’s true regardless of your location within the file system. It doesn’t matter if you’re in C:\Scripts; you still need to type the following:


Now, I said “in general” because there are a couple of exceptions to this rule. For example, if the script happens to live in the current directory you can start it up using the .\ notation, like so:


And while PowerShell won’t search the current directory for scripts it will search all of the folders found in your Windows PATH environment variable. What does that mean? That means that if the folder C:\Scripts is in your path then you can run the script using this command:


But be careful here. Suppose C:\Scripts is not in your Windows path. However, suppose the folder D:\Archive is in the path, and that folder also contains a script named script.ps1. If you’re in the C:\Scripts directory and you simply type script.ps1 and press ENTER, guess which script will run? You got it: PowerShell won’t run the script in C:\Scripts, but it will run the script found in D:\Archive. That’s because D:\Archive is in your path.
Just something to keep in mind.

How to run scripts without starting Windows PowerShell?
As a security measure you can’t start a PowerShell script by double-clicking a .PS1 file. So apparently that means that you do have to start PowerShell before you can run a PowerShell script. However, that doesn’t mean that you can’t start a PowerShell script from a shortcut or from the Run dialog box; likewise you can run a PowerShell script as a scheduled task. The secret? Instead of calling the script you need to call the PowerShell executable file, and then pass the script path as an argument to PowerShell.exe. For example, in the Run dialog box you might type a command like this:
There are actually three parts to this command:
Powershell.exe, the Windows PowerShell executable.
-noexit, an optional parameter that tells the PowerShell console to remain open after the script finishes. Like I said, this is optional: if you leave it out the script will still run. However, the console window will close the moment the script finishes, meaning we won’t have the chance to view any data that gets displayed to the screen.
Incidentally, the -noexit parameter must immediately follow the call to the PowerShell executable. Otherwise the parameter will be ignored and the window will close anyway.
C:\script.ps1, the path to the script file

Categories: MS Windows, OS Tags: ,

Enable multiple RDP connections per user in Windows Server 2012.

By default, Windows 2012 servers allow a single Remote Desktop session (exactly the same way as it was in Windows 2008).
If only one session is available and you take over another person’s live session, you may choose to enable multiple RDP sessions.

Below, you can find steps for enabling multiple sessions:
1. Open the start screen (press the Windows key) and type gpedit.msc and open it.
2. Go to Computer Configuration => Administrative Templates => Windows Components => Remote Desktop Services => Remote Desktop Session Host => Connections.
3. Set Restrict Remote Desktop Services user to a single Remote Desktop Services session to Disabled.
4. Double click Limit number of connections and set the RD Maximum Connections allowed to 999999 (maximum allowed).


Categories: MS Windows, OS Tags: , , ,

Desktop icons in Windows 2012 R2.

Here you can find my grumblings about desktop icons in Windows 2008R2.
Guess what? In Windows 2012R2 nothing really changed. Oh, wait – because it is the new version of Windows – adding desktop icons (My Computer for example) in Windows 2012R2 is even more complicated than before.
Anyway, first, you’ll have to go into Server Manager and under Manage, choose Add Roles and Features.

Then click Next on EVERY SCREEN until you get to the Features section, select Desktop Experience under User Interfaces and Infrastructure.

Once added, you will have to aprove installing other features required by Desktop Experience.

Then you need to reboot the server. That’s right! A reboot is required to add icons to your desktop.

Once you’ve rebooted the server, simply right-click on the Desktop and select Personalize. From here, you can add the desktop icons you desire as usual.

I’m speechless.