Hyper-V on Windows 8 (Pro or Enterprise)

Looking for a hypervisor on Windows 8? Look no further. If your Windows 8 is Pro or Enterprise Hyper-V is available as a feature, and can be enabled easily as long as your system complies with there requirements:

  • Windows 8 Pro or Windows 8 Enterprise (64-bit Operating System)
  • Minimum of 4GB of RAM
  • Hardware Assisted Virtualization (HAV) – (This may appear as Intel VT)
  • Dynamic Execution Prevention or No Execute (DEP/NX)
  • Second Level Address Translation (SLAT)


Open Windows Features to check if Hyper-V is enabled:



To enable the Hyper-V feature check the box and press OK:




When the Hyper-V feature is enabled your computer needs to be restarted:



After restart Hyper-V will appear on your Start Screen:



Hyper-V on your Windows 8 can be managed using Hyper-V Manager as any Hyper-V running on a Windows Server:


PDF Search missing in Windows 7 (64-Bit)

For some reason the 64-bit versions of Windows has a problem indexing PDF files. Windows Search uses IFilter to help it index files, and the PDF IFilter for 64-bit Windows is missing. (This probably applies to 64-bit Vista and 64-bit XP as well).

To detect whether a computer has the IFilter installed or not open Indexing Options from Control Panel:



Choose Advanced:



Find the PDF extension on File Types tab:


As shown above PDF Filter Description says Registered IFilter Is Not Found



To fix this problem download and install:

Adobe PDF iFilter 64-bit


When everything is installed your filter description for pdf extensions should say “PDF Filter” instead of “Registered IFilter Is Not Found” in Indexing Advanced Options:



Before being able to search PDF-files the Index has to be rebuild. This is done by clicking Rebuild i Indexing Advanced Options:




Please note: Rebuilding index can take a long time if your disks contains large amount of data.


Atheros AR5007 failed to connect (WiFi/Internet)

This behaviour is seen when connecting a Vista computer with Atheros AR5007 Wireless LAN adapter installed to a new wireless accesspoint. (In this case a HP laptop computer with preinstalled Vista Home Premium connecting to Cisco Linksys EA6500).

When inspecting network configuration you will find DHCP-address is assigned correctly – BUT no traffic is recieved on the wireless adapter. You are unable to ping any network devices, and renewing DCHP-address will also fail.
Other devices have no problem using the wireless network.

Install SP53261 from hp.com

This new Atheros Wireless LAN Driver will replace the preinstalled driver, and resolve the problem for these Atheros adapters:

  • Atheros AR5006 802.11a/b/g WiFi Adapter
  • Atheros AR5007 802.11b/g WiFi Adapter
  • Atheros AR5009 802.11a/g/n WiFi Adapter
  • Atheros AR9285 802.11b/g/n WiFi Adapter
  • Atheros AR9380 802.11a/g/n WiFi Adapter
  • Atheros AR9382 802.11a/g/n WiFi Adapter
  • Atheros AR9485 802.11 b/g/n WiFi Adapter


The new driver is compatible with a wide range of Windows versions:

  • Microsoft Windows 7 Enterprise 32 Edition
  • Microsoft Windows 7 Home Basic 32 Edition
  • Microsoft Windows 7 Home Premium 32 Edition
  • Microsoft Windows 7 Professional 32 Edition
  • Microsoft Windows 7 Starter 32 Edition
  • Microsoft Windows 7 Ultimate 32 Edition
  • Microsoft Windows 7 Enterprise 64 Edition
  • Microsoft Windows 7 Home Basic 64 Edition
  • Microsoft Windows 7 Home Premium 64 Edition
  • Microsoft Windows 7 Professional 64 Edition
  • Microsoft Windows 7 Ultimate 64 Edition
  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Media Center Edition
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Tablet PC Edition
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows Vista Enterprise 32 Edition
  • Microsoft Windows Vista Home Basic 32 Edition
  • Microsoft Windows Vista Home Premium 32 Edition
  • Microsoft Windows Vista Business 32 Edition
  • Microsoft Windows Vista Starter 32 Edition
  • Microsoft Windows Vista Ultimate 32 Edition
  • Microsoft Windows Vista Enterprise 64 Edition
  • Microsoft Windows Vista Home Basic 64 Edition
  • Microsoft Windows Vista Home Premium 64 Edition
  • Microsoft Windows Vista Business 64 Edition
  • Microsoft Windows Vista Ultimate 64 Edition


Browse FTP site in Windows Explorer (triggered from Internet Explorer 9)

By default the option to view FTP site in Windows Explorer is hidden in Internet Explorer 9 (IE9).

To enable it you have to go to Internet Options -> Advanced -> Enable FTP Folder View as shown below:

Once this option is enabled you should see Open FTP Site in Windows Explorer in the View-menu.
(Keep in mind that this option is only visible when you are on an FTP page).

Note: Press ALT to show Internet Explorer menus.

Blue Screen of Death (BSoD) when putting Windows 7 to sleep

All of a sudden my Windows 7 ended up crashing with Blue Screen of Death when put to sleep, and I started investigating this behavior.

After a couple of crashes a pattern started to emerge: Blue Screen of Death was only an issue when the laptop was running on batteries – and NOT when AC was plugged in.

This led me to investigate the memory crash dump using Debugging Tools for Windows which indicated the problem was probably caused by dne64x.sys (part of DNE – Deterministic Network Extender)

Even though Citrix indicates DNE is practically flawless…..

With tens of millions of copies of DNE installed and over 12 years in the market, there are no known crash issues with DNE. However, because DNE is a kernel-level NDIS module that relies on packets from other drivers, we sometimes see crashes that appear to be in DNE. Generally these are caused by bugs in other products or drivers

… I decided to reinstall DNE using Citrix guidelines:

  1. Uninstall programs using DNE
    Citrix suggest trying to uninstall the program that uses DNE (e.g. a VPN client) before reinstalling DNE.
  2. Run Winfix
    Run the Citrix utility called Winfix (ftp://files.citrix.com/winfix.exe) that can clean up most Windows operating systems to enable installation of products that use DNE and other products like DNE.
  3. Download and install the latest DNE
    32-bit: ftp://files.citrix.com/dneupdate.msi
    64-bit: ftp://files.citrix.com/dneupdate64.msi
  4. Reinstall the product that uses DNE


This solved the problem – and my laptop sleeps tight again without crashing!


Write Event to Windows Event Log using PowerShell


Creating an EventLog entry using PowerShell is shown below:

Write-EventLog -LogName 'Application' -Source 'MyEventSource' -EventID 1000 -EntryType Warning -Message "This is a test of writing to the Event Log using PowerShell."


Note: The Event Source needs to be created before writing entries to the Event Log. (See this post for further info: Create Event Source with PowerShell)



Useful command lines to access different parts of Windows Control Panel

Use these commands (.cpl) to gain fast access to different part of the Windows Control Panel:

Action Center                   wscui.cpl
Add/Remove Programs             appwiz.cpl
Date/Time Properties            timedate.cpl
Device Manager                  hdwwiz.cpl
Display Properties              desk.cpl
Fonts Folder                    fonts
Internet Properties             inetcpl.cpl
Game Controller Properties      joy.cpl
Keyboard Properties             main.cpl keyboard
Mouse Properties                main.cpl
Network Properties              ncpa.cpl
Pen and Touch Properties        tabletpc.cpl
People Near Me Properties       collab.cpl
Phone and Modem Properties      telephon.cpl
Power Management                powercfg.cpl
Regional Settings               intl.cpl
Sound Properties                mmsys.cpl
System Properties               sysdm.cpl
Windows Firewall Properties     firewall.cpl

Create Event Source with PowerShell

To create a Event Source in PowerShell use this:

$Source = "MyEventSource"
if ([System.Diagnostics.EventLog]::SourceExists($Source) -eq $false {
  [System.Diagnostics.EventLog]::CreateEventSource($Source, "Application")

Get more info on CreateEventSource method here : http://msdn.microsoft.com/en-us/library/2awhba7a.aspx


In PowerShell 2.0 this is even simpler:

$Source = "MyEventSource"
New-EventLog -LogName Application -Source $Source


Enumerate COM classes using WMI


Quick and short way of enumerating COM classes is using the WMI class Win32_ClassicComClassSetting.



Get-WmiObject win32_ClassicComClassSetting | Select-Object ProgID | Group-Object ProgID | Select-Object Name | Sort-Object Name


EventLog: Determine Windows startup (Event Log Service)

To determine when Windows was started search for Event ID 6005 in the System Event Log. The entry should look like this:

Log Name:     System
Source:       EventLog
Event ID:     6005
User:         N/A
Computer:     computername
Description:  The Event log service was started.