Outlook blocked access to the following potentially unsafe attachments...

Issue

A user receives an email with some PDF files attached. Attachments are not accessible in MS Outlook 2010. Instead, following message is displayed:

Outlook blocked access to the following potentially unsafe attachments: Important! Invoice 721.pdf, Important! Invoice 721.pdf.

Workaround

This MS Outlook behaviour is a bug introduced by 13 June 2017 Outlook Security Update, and affects all recent versions of MS Outlook (2007 - 2016). In this particular case the bug was triggered by attachments having an exclamation mark in their file names and the offending update was KB3203467.

Event 11 - The driver detected a controller error on \Device\Ide\IdePort

Issue

Computer randomly becomes unresponsive or very slow without any apparent reason. System even logs are full of following errors:

Event ID: 11
Level: Error
Description: The driver detected a controller error on \Device\Ide\IdePort4.

Convert VMware vmdk disks to Hyper-V vhdx

• Download and install Microsoft Virtual Machine Converter 3.0
• Start Windows PowerShell as administrator
• Import the converter's PowerShell module: 
  

  Import-Module 'C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1'

• Convert vmdk disk to vhdx:
  

  ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath "D:\SOURCE_PATH\VMware_Disk.vmdk" -DestinationLiteralPath "D:\DESTINATION_PATH\Hyper-V_Disk.vhdx" -VhdType DynamicHardDisk -VhdFormat vhdx

Must be run on Windows 6.2 (Windows 8 / Server 2012) or later OS.

Issues with VMware Workstation VMs on Windows Storage Spaces

I recently configured a Windows 10 (1703) PC with Storage Spaces in 2-way mirror mode. The Storage Spaces drive hosted some Hyper-V and VMware Workstation 12.5 virtual machines. While Hyper-V VMs worked fine, VMware Workstation started causing trouble from the beginning.

At first I notices issue with Linux Virtual Machines. They would install and start correctly one or two times, but then refuse to boot. Even restoring a snapshot that was taken while machine was still in bootable state didn't help. Linux Machines would either crash during boot with Kernel Panic, or (in case of Ubuntu) boot into Low Graphics mode and only work in terminal.

The system is running in low-graphics mode
Your screen, graphics card, and input device settings could not be detected correctly. You will need to configure these yourself.