This morning when I logged in I received the following notice in my task bar: “Windows 10 Upgrade Notification”
To register it for your Free Windows 10 Upgrade simply click Reserve and fill out your email:
You will receive confirmation upon sucessfull registration:
At the time of this post I am running Windows 8.1 Pro 64-bit.
Microsoft changed many features with Windows 8, one of those many features is how a Restore, Reset and Recovery are done. I personally am very happy with the new feature in Windows 8. To use any of the methods; Restore, Reset, Recover you must first ensure you’ve created a backup DVD or USB image.
When Resetting your PC Microsoft now provides you with the option to reset the Windows Drive (AKA the OS Drive) or All Drives.
This is an extremely useful option because many intermediate to advanced users may run their Windows on one drive and store data on secondary drives (other physical drives). By storing data on separate drives a user can Reset or Recover Windows without losing data.
Moving along, another great feature when Resetting your Windows 8 PC is that Microsoft now provides the option to “Fully clean the drive” (erases all data) or “Just remove my files” (erases your data however in some cases can still be recovered).
I like this feature because it comes in handy when someone may be selling or giving away a computer. “Fully clean the drive” means that Microsoft will apply a more thorough hard drive wipe (format), some call it a low level format. This makes it more difficult for people to recover data from a hard drive. Ultimately protecting the end-user should someone attempt to recovery data.
The full clean option also helps in situations where your computer may be experiencing problems. In rare occasions I have had to format (Fully clean the drive) the hard drive to re-install Windows, again this is very rare as sometimes a quick format doesn’t put the drive into a state in which Windows will install.
The other day I built a Virtual Machine to test errors I experienced in Outlook 2010. I applied the latest Windows Updates to the Virtual Machine however when I was prompted to update .NET 4.5.2 (KB2901983) I received the error code 13EC.
To resolve the Windows Update error code 13EC for KB2901983 I had to expand the virtual drive. My Virtual Machine had roughly 2 GB free prior to applying the update so I expanded the virtual disk by 5 GB and the update applied successfully.
If you have a physical machine then the issue is likely your C drive (operating system drive) is either full or to small.
Microsoft answers.microsoft.com has a related post: click here.
Over the weekend I decided to install Fedora Core 21 Server on my Windows 8.1 home server running Hyper-V. I was able to install Fedora Core 21 Server without having to run Linux Integration Services which is very nice as network, mouse/keyboard, hard drive functions work “out-of-the-box.”
On initial installation I disabled “Secure Boot.” In most cases I find that UEFI “Secure Boot” for Linux Virtual Machines in Hyper-V does not work.
Fedora Core 21 must have built in kernel support for Hyper-V however I have not been able to find any official documentation regarding “native kernel support for Hyper-V.” Fedora Core is similar to Red Hat and Cent OS so I am assuming the development team has included native kernel support for Hyper-V, as they do with the newer releases of Red Hat and Cent OS.
It is worth noting that Hyper-V does not report Integration Services status or an IP address via the Hyper-V management console. Based on my experience with Hyper-V only Window’s Virtual Machines are reliable when reporting status such as Integration Services, Network IP, Heartbeat, etc.
Microsoft Tech Net highlights Linux Virtual Machine Guest Operating System Support here. Note that Fedora Core is not amongst the supported guest operating systems.
I also tried installing Fedora Core 21 Workstation which did not work. The Cloud version of Fedora Core 21Cloud requires a different environment in order to be deployed (openstack).
Yesterday I discovered an issue on my Dad’s RAID1 array. In order to rebuild the array I had to download the AMD RAIDXpert Utility. The AMD RAIDXpert Utility was not easy to find at least not initially. Making matters worse the bios RAID controller GUI does not currently provide a rebuild option.
My fathers desktop is a custom built workstation and uses the motherboards onboard RAID controller. The factory disk which contains the motherboard drivers did contain the AMD RAIDXpert Utility however it didn’t contain the latest and greatest version which I needed for Windows 8. Making matters worse the motherboard vendor also did not provide the latest AMD RAIDXpert Utility for Window’s 8.
Fortunately after some good old Google searches I found the following forum post How to fix missing RAID1 drive. Within the post was a link to the AMD website which provided the download for the latest and greatest AMD RAIDXpert Utility. To download the AMD RAIDXpert Utility click here.
After finally fixing the issue and reviewing the AMD Drivers Download page I see how I initially missed the AMD RAIDXpert Utility…
Step 1) Navigate to the AMD Download Drivers webpage
Step 2) Use the link for your OS on the right hand side of the “Manually Select Your Driver.”
Step 3) Now select the optional downloads tab and scroll to the bottom. Download the AMD RAIDXpert Utility
If you are unable to find the download I would highly recommend reaching out to AMD support.