DisplayPort and Windows Positions

[sc:hardware-category ]I’ve been running my 4K monitor for a while now and I connected it through DisplayPort.  This was the first time I’ve used DisplayPort (my old monitor was connected through HDMI) and whenever I turned off the monitor all my window positions reset to the top left corner.

This was strange but hunting around the next for a while I found some information that basically indicated it was because Windows treats DisplayPort devices just like any other hot plug device and when you turn off the monitor it effectively “removes” the display from Windows.

Of course this means Windows drops back to its default display driver, which happens to be 1024×768, hence all the windows shrinking to fit in that display size.

Microsoft has a KB on the issue, but in the end the options are basically:

  1. Live with it
  2. Let the monitor go to sleep instead of turning it off
  3. Shutdown the system when you want to turn the monitor off
  4. Don’t use DisplayPort

At the moment I’ve opted for #2, just letting the display go to sleep which seems to work alright.  My only concern is with power outages if I didn’t have the monitor on the a UPS,  but I have both the monitor and PC on an UPS so that shouldn’t be a problem.

I may just go back to HDMI, it works fine with 4K displays and doesn’t appear to have the issue.

Windows Patching KB3002885

[sc:windows-category ]Last month Microsoft released several patches and KB3002885 was included in the list.  When my 2012 servers applied the patches, this patched failed.

To compound the issue, when a single patch fails, Windows rolls back all the patches that were applied at the same time.

This meant that every couple of nights, my servers would reboot and try once more to apply the patch, fail and roll back the changes.

I didn’t have time to look at the problem until recently and really just kind of expect Microsoft to release a new version of the patch which would solve the issue, but that hasn’t happened so it was time to do some investigation.

Checking the “Update History” revealed a couple of different error codes (80073AA2 was common), which didn’t really seem to help, so the first step was to track down exactly which update was failing (Windows doesn’t tell you which one failed, it just marks them all as failed).

While a simple task (just select half the updates and see if it fails, if so select half of those and try again) it does take quite a while to go through the 20 updates and find the one that was broken.  In the end it as the patch for KB300285 that was failing.

Doing some research didn’t turn anything obvious us, but after searching the net for a while I did find a reference to a similar problem being caused by corruption in registry, specifically the HKLM\Software\Microsoft\Windows\CurrentVersion\WINEVT hive.

The general consensus was to simply delete the entire hive, instead I renamed it and then re-applied the patch, which worked.

Windows recreated the hive with much less information in it, doing a quick comparison to the original hive turned up only a single key that was missing.  I exported that key (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{8c416c79-d49b-4f01-a467-e56d3aa8234c}), deleted the new hive, renamed the old one and re-imported the changes.

On my next server I decided to try and just import the missing key and then apply the patches, but that didn’t work.

I had to rename the hive and apply the patches on each of the servers by hand.  While this was tedious, it has resolved the issue.

 

Windows 10

[sc:windows-category ]With any product that has been around for a few years, numbering always becomes a problem.

When first released, numbers are technically significant, you want to see the “1.0” release before you really start relaying on it and your excited to “2.0” for all the new features that were missing from “1.0”.

But then it starts to lose that meaning, is 6.0 really all that different from 7.0 or 9.0?

Microsoft has clearly understood this with the next release of Windows and decided to jump straight to 10 from 8.

It’s a pretty slick move really, it makes it clear it’s still Windows but is a big enough bump to separate it from previous releases.

The technical preview is focused pretty much on the enterprise clients so they’re left out quite a bit of the end-user features, but they have detailed some of them.  Also it looks like a least next summer before a release so we’re going to have a long wait to see something close to a final release.

Start Menu

Yes it’s back and it kind of looks like a Windows Phone start page.  I guess after the uproar of Windows 8 they had to bring it back, but I hope they still support the start page on desktops as well.

I do like the start page, I think it provides a much better interface even on a desktop, but I’m obviously in the minority there 🙂

Windowed Modern Apps

Just like the start menu, it only makes sense to make the modern apps work on the desktop in windowed mode.  I’d be using more modern apps if they did.  Now it looks like I’ll get my wish!

Multiple Desktops

Unix and Mac have had multiple desktop support baked in for years and it has been an option through third-party software for Windows, but Microsoft has included it in 10.  I’ve never been a fan of multiple desktops, but I understand why many people will find this a great addition.

Paste in to the Command Prompt

The command prompt has always been a pain if you want to copy and paste stuff around, Windows 10 now lets you use Ctrl-V to paste text from the clipboard directly in to the command window!

Charms Bar

I like the charms bar, but many people found it to be less than useful.  Microsoft is keeping it in Windows 10 but they’re going to be changing it in some unspecified manner before release.

 

BitLocker Recovery

[sc:windows-category ]Recently I went on vacation to Europe for two weeks, I of course took my laptop with me and as always I have BitLocker enabled.

The trip started off with all the classic travel issues you might expect, family emergency at the last-minute, hotel booking being cancelled without any notification and a near death experience at the airport.

However by the second night things had seemed to be going well and I went to bed for a good nights sleep.  The next morning I booted up my laptop to check e-mail and was greeted with the BitLocker Recovery screen.

Normally that wouldn’t be a big issue, my recovery keys are stored safely at home and I’d be able to grab a friend’s computer to use to get them.  Of course, on vacation that became a bit more of an issue…

My first thought was to check OneDrive, but I didn’t place them there and still believe that to be a bad idea.

Next was to see if I had opened RDP to my home computer as I have the RDP client on my phone unfortunately I hadn’t and so that failed.

I do have SSH available to my Linux box and so I opened the Store on my phone and find a SSH client, which I did.  However it turns out I hadn’t installed the packages needed to get access to a Windows file share and trying to use the SSH client was problematic on the phone as it’s keyboard was limited and every time I switch to the web browser to look something up it disconnected me.

Finally I gave in and went out looking for an Internet café I could use.  The first one was packed, the second one had several stations available.  They were running XP but it had most of what I needed.  I downloaded Putty, connected to my Linux box, used the port forwarding in Putty to then RDP to my PC and retrieve my recovery key.

My laptop booted up cleanly after that and I didn’t find anything wrong.  I still don’t know why it needed the recovery key but it’s been fine since them.

Dell Venue 8 Pro and ASUS Miracast adapter

[sc:hardware-category ]When I purchased my Dell Venue Pro 8 I didn’t notice that it supported Miracast and quite honestly it wasn’t a feature I was really looking for as the only Miracast adapters were far too expensive.  Recently that’s changed.

I started looking for a Miracast adapter a while ago for my notebook, but I was unsure if it supported Miracast and didn’t want to shell out $150+ to find out for sure.  However I found the ASUS Miracast Adapter for a reasonable $56.99 over at Mike’s Computer Shop so I decided to take a chance.

The adapter comes with everything you need, a 90 degree HDMI adapter, a MicroUSB cable and power adapter and the Miracast adapter itself.

Plugging it all in was easy enough and in just a couple of seconds I had it waiting for a connection on my TV.  The ASUS unit displays on-screen instructions on how to connect to it, however it does assume your running an Android tablet.

Windows 8.1 has Miracast support built-in and swiping in from the right and selecting the devices charm let’s you project your screen on to the Miracast adapter.

The ASUS adapter uses a very long and complex name, which includes the device firmware version in it.  It’s a bit of a weird choice on ASUS’s part, but not a big deal overall.

After connecting the display is duplicated and everything worked fine… for about 30 seconds and then promptly disconnected.

This happened every time I connected to the adapter.

I decided to check the ASUS support site but there was nothing talking about disconnects, there was however a new firmware version.

If you’re using an Android tablet, firmware updates are pretty easy to do.  Otherwise you have to connect to the Miracast adapter via WiFi and manually upload the new firmware to the device.

It didn’t take long and after a few minutes it was back up and running.

After the update though the name of the adapter changed as the new firmware was no reflected in the adapter name.  This required me to delete it from my Venue and re-add it.  An annoyance at best but worth the effort as the firmware update resolved the disconnecting issue.

Once everything was up and going, the display was crisp and reasonably responsive.

Windows 8 on the Venue Pro is a very smooth experience in general, but the overhead of Miracast does make it a little jerky.  Nothing that makes it impossible to use, just not the butter smooth experience it usually delivers.

So far everything I’ve tried; Netflix, YouTube, Windows Media Player and more, has worked just fine.

Over the years I’ve tried to find a good media center PC to drive my TV, but I may have found a better solution in Miracast.

The only one small grip with the ASUS dongle is how wide it is near the HDMI port.  One TV I tried it on had another port right beside the HDMI connector and the ASUS adapter just would not fit.  Other than that, it does run a bit hot, but works quite well.