Dell Broadcom USH Drivers

This always happens to be when I do a fresh install of Windows on a Dell notebook…

Dell’s got a page now with drivers for most of their recent computers:

Download here: https://www.dell.com/support/article/us/en/19/sln129590/download-the-broadcom-ush-drivers-and-resolve-unknown-device-issues?lang=en

These are the ones I use the most.  Windows 10 x64 drivers for the Latitude e6540, e7240, e7440, and Precision M4800, Latitude e7270

Advertisement

Hyper-V VMGuest.iso for older Windows OSes in Win10/2016

If you’re playing around with older OSes in the latest versions of Hyper-V, you’re missing one thing, the Integration Components (IC).

With Win10/Server2016 they no longer include this ISO as the current “supported” OSes all get their IC viaWindows Update.

You can get the IC from Hyper-V 2012/2012R2 Server, a free download, here:

https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2012-r2 ( to extract, you’ll need to mount the ISO, open the x:\sources\install.wim file with something like 7zip, browse to Windows\system32, and extract the vmguest.iso or install Hyper-V Server in a VM to get the vmguest.iso)

Or, if you’ve got a Windows 8/8.1/2012/2012R2 VM/system available with Hyper-V installed you’ll find it in the C:\windows\system32\ folder.

I’ve got a copy from Hyper-V 2012 R2 here: https://1drv.ms/u/s!AnbqFQxI6C6pibttEpT9LXnRf4jcYg 

Hyper-V 2008 R2 here: https://1drv.ms/u/s!AnbqFQxI6C6pio4TpkS4Yi9Pl0_Ejg 

Hyper-V 2008 here: https://1drv.ms/u/s!AnbqFQxI6C6pio4UYt3Jn_VLbrQs4w

No guarantees how long MS will allow it will stay up here, though it’s freely distributed with Hyper-V Server.

After installing the IC on OSes older than Windows Server 2012R2,  you will still see 2 unknown devices.  Per Microsoft, this is expected: https://support.microsoft.com/en-us/help/2925727/unknown-device-vmbus-in-device-manager-in-virtual-machine-for-avma

If you view the properties of these devices and check driver details, Hardware IDs or Compatible IDs, they will show the following:

• vmbus\{4487b255-b88c-403f-bb51-d1f69cf17f87}
• vmbus\{3375baf4-9e15-4b30-b765-67acb10d607b}
• vmbus\{99221fa0-24ad-11e2-be98-001aa01bbf6e}
• vmbus\{f8e65716-3cb3-4a06-9a60-1889c5cccab5}

These Virtual Devices (VDev) are provided for Automatic Virtual Machine Activation (AVMA) to communicate with the host. AVMA is only supported on virtual machines running Windows Server 2012 R2 or later versions of operating systems.

Windows XP Pro running in Hyper-V. Device Manager shows the 2 unknown devices after the IC have been installed.

—

Update:  The Integration Components won’t install in the Home and Starter versions of Windows.

TinyBorders for Win8 replaced with Winaero Tweaker

I posted a while back about a nice little utility I use on all my Windows 8.x systems to reclaim those lost pixels from Win 8’s giant, padded borders.

It’s recently been replaced with a new tool, Winaero Tweaker, link: http://winaero.com/comment.php?comment.news.1836

A new feature with Winaero Tweaker allows you to change colors, which is nice when working with Windows Server 2012 R2.

If you try to change the color you’ll see this:

 

Winaero Tweaker launches with an error in Windows Server 2012 R2, but it doesn’t seem to affect the programs ability to change border size or color.

As you can see, I changed the color from cyan to a light purple, shown in the Winaero Tweaker page

 

 

 

 

TeamViewer + Windows 8.1+AMD switchable graphics = black screen

I use TeamViewer a lot, both for work (with a purchased license) and the free version for home.  Recently, on my home machine, a Dell e6540 whenever I’d connect to it, all I’d see was a black screen. Connecting to another laptop, a Dell e5520, was no problem.

One thing I thought could be an issue was the AMD switchable graphics, so I set the teamviewer_desktop.exe to use the more powerful AMD Radeon HD 8790M.  Made the switch and no luck.  So I asked Google, and found a superuser.com thread (http://superuser.com/questions/777492/teamviewer-other-screen-sharing-showing-a-blank-or-black-screen-to-remote-user)  that said to do the exact opposite, set teamviewer_desktop.exe to use the Intel graphics.

That was the trick, with teamviewer_desktop.exe set to Power saving, TeamViewer functions normally.

Go to the AMD Catalyst Control Center, then Switchable Graphics Application Settings.  If TeamViewer_Desktop.exe is not listed, click Add application and browse to your TeamViewer installation (default is C:\Program Files (x86)\TeamViewer) select Power Saving and click Apply.

Dell Wireless TouchPad

I purchased the Dell Wireless Touchpad sometime last year after I moved my primary workstation to Windows 8.  I didn’t really start using it much until lately.

I’ve found it’s a great add-on to the mouse and keyboard when working with Windows 8 on a multi-screen setup.

I mainly use it for the left and right edge sweep to get to the Charms bar or to switch between programs.  I wouldn’t give up my mouse for this, but it’s definitely a value add for only $30.

 

 

 

 

Charms Bar

Windows 8 Tweaks Part 2

in my earlier post,  Windows 8: Tweaks, I mentioned a Registry fix for the fat border issue with Windows 8.

I’ve found a simpler solution, there is a little tool, Tiny Windows Borders for Windows 8

This is a GUI interface for adjusting the Border Width and Border Padding for Windows 8.x.  Easier than messing with RegEdit!

Also, if you want to slim down those outrageous title bars in Windows 8, the process is simple as well.

Right-Click the desktop, select Personalize, Click Display on the left side of the Personalization Window. (Per feedback, I’m including more pictures in my posts.)

Next, under Change only the text size, select Title Bars and reduce the font size to your desired size, even going down to 10 makes a visible difference.

 

Also, another thing I like to do after I install Start8 or StartIsBack is to restore the quick launch menu.  I have had this tip on my old website www.essjae.com for a long time, but here it is again.

• Right-click the Taskbar, select Toolbars–>New Toolbar.
• In Folder text box copy and paste the following:
      %userprofile%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch
• Right-click the Taskbar, uncheck Lock the Taskbar, and right-click on the new Quick Launch toolbar. Uncheck Show Text and Show Title, click View–>Small Icons
• Drag the toolbar divider all the way to the left of the taskbar to position it next to the Windows Orb, adjust the spacing on the taskbar as necessary
• End result:     
• Note: the default quick launch is pretty slim, most of the icons above were manually added

Windows Update fix for corruption errors like 0x80070002

Microsoft KB 947821 (http://support.microsoft.com/kb/947821)

If you’ve gotten one of those cryptic 0x800xxxxxx Windows Update errors, Microsoft finally has a fix for Vista and higher, no XP solution.

Fix Windows Update corruption errors such as 0x80070002 and 0x80070057

Windows Update corruption errors prevent Windows updates and service packs from installing. For example, an update might not install if a system file is damaged. If the error you see is in the following list, try the solution in this article.

0x80070002 | 0x8007000D | 0x800F081F | 0x80073712 | 0x800736CC | 0x800705B9 | 0x80070246 | 0x8007370D | 0x8007370B | 0x8007370A | 0x80070057 | 0x800B0100 | 0x80092003 | 0x800B0101 | 0x8007371B | 0x80070490

 

Windows 8.x and Server 2012 Rx

To resolve this problem, use the inbox Deployment Image Servicing and Management (DISM) tool. Then, install the Windows update or service pack again.

1. Open an elevated command prompt. To do this, swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. Type Command Prompt in the Search box, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
2. Type the following commands. Press Enter after each command.
   Note It may take several minutes for each command operation to be completed.
   • DISM.exe /Online /Cleanup-image /Scanhealth
   • DISM.exe /Online /Cleanup-image /Restorehealth
3. Close the command prompt, and then run Windows Update again.

DISM creates a log file (%windir%/Logs/CBS/CBS.log) that captures any issues that the tool found or fixed. %windir% is the folder in which Windows is installed. For example, the %windir% folder is C:\Windows.

 

Windows 7, Windows Vista, Windows Server 2008 R2 or Windows Server 2008

See the KB link for the download you need. http://support.microsoft.com/kb/947821

Virtual Machines not shutting down on host shutdown in Windows Server 2012 R2

Ben Armstrong has a little blurb about  a fix included in the latest rollup for Windows Server 2012 R2

http://blogs.msdn.com/b/virtual_pc_guy/archive/2014/01/08/virtual-machines-not-shutting-down-on-host-shutdown-in-windows-server-2012-r2.aspx

http://support.microsoft.com/kb/2896800/en-us

Hyper-V guest OS does not shut down when you restart the host computer that is running Windows Server 2012 R2 or Windows 8.1

Symptoms

Consider the following scenario:

• You set up a Hyper-V virtual machine on a host computer that is running Windows Server 2012 R2 or Windows 8.1.
• You set the Automatic Stop Action setting of the virtual machine to Shut down the guest operating system.
• You restart the host computer.

In this scenario, the guest operating system (OS) on the virtual machine does not shut down. Additionally, after you restart the virtual machine, the following event is logged on the guest OS:Event ID: 6008
Message: The previous system shutdown at time on date was unexpected.

Note If the computer is part of a cluster, this issue does not occur.

Cause

This issue occurs because the Virtual Machine Management Service tries to shut down the virtual machine by using the Virtual Machine Worker process. However, the process encounters a logic failure that causes the shutdown operation to fail and reverts the shutdown operation. Therefore, power cycling occurs instead of a clean shutdown.

Resolution

Update information

To resolve this issue, install update rollup 2887595. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:

2887595

(http://support.microsoft.com/kb/2887595/ )

Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: November 2013

“Not enough memory” error message and Windows Phone 8 Emulator does not start in Windows 8.1

There is a recent KB that addresses some issues that have appeared every so often on the TechNet forums.  Since the WP8 emulator uses Hyper-V any related memory issues with running Hyper-V VMs on 8.1 should also be covered by this.

“Not enough memory” error message and Windows Phone 8 Emulator does not start in Windows 8.1

http://support.microsoft.com/kb/2911380

The Windows Phone 8 Emulator does not start on a computer that is running Windows 8.1 and that has fewer than 8 gigabytes (GB) of RAM if many programs are running at the same time. Additionally, you receive the following error message:
“The Windows Phone Emulator wasn’t able to ensure the virtual machine was running:

Something happened while starting a virtual machine: ‘Emulator Name’ could not initialize. (Virtual machine ID GUID)
Not enough memory in the system to start the virtual machine Emulator Name with ram size 1024 megabytes. (Virtual machine ID GUID)”

Additional troubleshooting can be found here:  https://smudj.wordpress.com/2013/02/22/troubleshooting-windows-8-and-hyper-vwindows-phone-8-emulator/

Updated Surface Pro Wacom Driver

Just saw the Facebook posting of how great the Surface Pro 2’s pen is, and I thought that I must really have a really poor digitizer on my original Surface Pro.  I followed the link to the Wacom site and found a new driver.  Installed it and my pen is much more accurate now than it was.  There’s a new calibration process as well.  If your Surface Pro pen experience is lacking, give this a try!

http://us.Wacom.com/en/feeldriver

TABLET PC – Enhanced Tablet Driver 7.1.2

Expand the capabilities of your Windows 8 and Windows 8.1 tablet computer. Installing this driver will provide many advanced pressure-sensitive features that Wacom pen tablet users have come to enjoy. The driver supports advanced features such as pressure-sensitivity in graphics applications such as Adobe Photoshop and Corel Painter. It also allows you to adjust the pen tip pressure sensitivity and to program the side switch of the pen for a wide range of alternative settings and functions.

This driver should be installed on tablets that have Wacom feel IT technologies or Wacom Pen based technologies. This driver will also support older Penabled Tablet PCs running Windows 7, Windows Vista, and Windows XP Tablet Edition.

Driver installation

1. Click on the Download link and save the file to your computer. If you are upgrading from a previous Wacom driver version, uninstall that driver first for best results. Restart the system prior to installing the new driver.
2. Double-click on the downloaded file to launch the installer and follow the prompts.
3. If prompted, restart the system by clicking the Ok button.

View the Driver Read Me information

>>Download Driver<<