FIX: “Hyper-V encountered an error trying to access an object on computer ‘localhost’ because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running. If the service is running, try to perform the task again by using Run as Administrator.”

Opened up Hyper-V today and all of my VMs where missing… umm what?

HyperV missing 1

So I tried to connect to a server (button far right)

HyperV missing 2

POPUP ERROR

 HyperV missing 3

Error Text

“Hyper-V encountered an error trying to access an object on computer ‘localhost’ because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running. If the service is running, try to perform the task again by using Run as Administrator.”

Troubleshooting

Checked Services they are running

Checked optional components they are running

Tried to run PowerShell Get-VM… ERRORS!

Long story short it turns out that a recent uninstall had deleted a MOF

Fix

Run the following command from an Elevated (Administrator) command prompt or PowerShell.  Winkey+X >> Windows PowerShell (Admin)

MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof

Summary

Sometimes an uninstaller for an application has unintended consequences!  Good news it was an easy fix of just recompiling the MOF (Microsoft Object Format).  WMI is awesome but so touchy.

 

Advertisements

Workaround: Road Warrior Long logon / logoff times / Guest WIFI portal missing – What is causing them and a quick work around

I travel for work… a lot.  Which means I am connecting to a lot of WIFI networks.  Yes, I know security issues but hey I have to get work done no matter where I am.

Issue: Long logon / Logoff and Guest WIFI redirects failing

Recently, I was experiencing extraordinarily long Logon and Logoff times.  It was highly infuriating and I didn’t have a clue what was causing it.  A little digging gave me a method to see what was taking so long.  This also led me to why I couldn’t connect to wifi gateways for guest logon.

Enable Verbose Logon Status Messages

To use enable verbose status messages by editing the registry, follow these steps:

  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  4. On the Edit menu, point to New, and then click DWORD Value.
  5. Type verbosestatus, and then press ENTER.
  6. Double-click the new key that you created, type
    1 in the Value data box, and then click
    OK.
  7. Quit Registry Editor.

Note Windows does not display status messages if the following key is present and the value is set to 1:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableStatusMessages
With this enabled I noticed I was having a long time with network configurations as it was running through the entire network stack history.

Solution?

The easiest method to clear the history is to run the following command line:
NBTStat -R
Note: -R is capitalized
-R (Reload) Purges and reloads the remote cache name table
Why just clear out the stack versus figure out the sort order?  Well, mainly for expediency.  Every time I connect to a network I only care about the network I am connecting to at that moment.  As the initial logon process works well… but reconnecting to a history network didn’t…
tb7ktx6

Side Effects

During the 1803 upgrade I noticed a new user logon status message I hadn’t seen before: Waiting for Workplace Connectivity.  More research coming…
2018-04-30 17.50.12

Windows 10 Feature Update 1803 – Initial deployments sneaking out?

The offical announcements for Windows 10 1803 have not gone out.  However, it looks like there are a few canaries in the coal mine getting the 1803 update directly from Windows Update.  In my case I forced a full update in the control panel and pop up comes Feature update to Windows 10, version 1803

The build number is 17134.1 which matches the most recent builds on Flighthub

For good or bad, it had NO names associated with the 1803 release.  Just New Feature Update.  So I was kind of correct here

 

I would expect announcements and more buzz here soon.

#WindowsInsiders #WindowsUpdate #Windows10 #WaaS #1803 #Windows1803 #Windows101803 #MVPBuzz

 

Windows 1803 release

 

 

Windows as a Service and 1803 Update – Will it continue have a marketing name?

I have been enjoying the constant name ruminations around Windows 10 1803 update.  The names I have seen flying around are getting hilarious.

TL;DR – There is NO offical name of the Windows 10 1803 release.   This doesn’t mean there won’t be one… just not one yet.

Previous Names for 1803

  • Feature update to Windows 10, version 1803
  • Microsoft Windows 10 Update/Server 1803
  • Microsoft Windows 10 Spring Creators Update/Server 1803
  • Redstone 4
  • April Update

What does Microsoft currently call it?

Turns out you just need to have the newest build of Windows Insider current release installed and run an elevated PowerShell prompt of

Get-VMHostSupportedVersion

The current results of build 17134.1

Name                                                      Version IsDefault
----                                                      ------- ---------
Microsoft Windows 8.1/Server 2012 R2                      5.0     False   
Microsoft Windows 10 1507/Server 2016 Technical Preview 3 6.2     False   
Microsoft Windows 10 1511/Server 2016 Technical Preview 4 7.0     False   
Microsoft Windows Server 2016 Technical Preview 5         7.1     False   
Microsoft Windows 10 Anniversary Update/Server 2016       8.0     False   
Microsoft Windows 10 Creators Update                      8.1     False   
Microsoft Windows 10 Fall Creators Update/Server 1709     8.2     False   
Microsoft Windows 10 Update/Server 1803                   8.3     True

New Naming Standard going forward?

The following is total speculation by me.  I believe the titled marketing names like Creators, Anniversary, etc are done.  As Microsoft embraces Modern nomenclature the names will really just be year and Spring or fall.   Why Spring or Fall versus 1803/1809?  Because we are already in Late April (1804) and we have had several blockers to release and dates slip.  I would rather Microsoft ship a great stable release than be beholden to a date name.  Spring and Fall gives them a celestial 3 month window to get it out the door.

#MVPBUZZ #WINDOWSINSIDERS #W101803 #Windows10

Fixed: OneDrive for Business agent running at 25% CPU after the most O365 Patches

Investigation

In January 2018 I noticed a severe impact to my laptop performance. This past week the process Groove.exe (OneDrive For Business) is constantly using 25-40% of my CPU.

OdFB - 1

There are no files to be sync’d and it just constantly states processing changes.

OdFB - 2

I have seen a few threads online stating this may be due to a recent O365 patches.

Pausing sync does NOT reduce CPU utilization.

Exit did not kill the process for over 60 seconds

OdFB - 3

 I did NOT want to do a library repair as I have like 4gb of data sync’d.

Onedrive for Business AUTO RESTARTS after about 5 minutes and right back to 25% CPU

SOLUTION

Update the OneDrive for Business agent!

Who do you tell if you have the older version?

Go to the taskbar and RIGHT click on the OneDrive for Business icon.  If you see text that says Repair as an option… you have the old one (didn’t get a screen capture before writing this blog)

How do I get the new OneDrive for Business Client?

Open PowerShell ISE (Windows Key + X) (NOT as an administrator)

  • This needs to be run in your user context
  • ACTION: Modify the script below with the correct Email Extension

$ODuser = $env:UserName

write-host $ODuser

$ODPath = $env:LOCALAPPDATA\Microsoft\OneDrive”

write-host $ODpath

#Change the EmailExtension

$ODURL = “odopen://sync?useremail=$ODuser@WORKEMAIL.com”

write-host $ODURL

Start-Process “iexplore.exe” “$ODURL

#Start-Process “explorer.exe” “$ODURL” 

What the new client looks like

OdFB - 4

Yea no more CPU spikes or sync errors!

Resolved: Feature update to Windows 10, version 1709 – Error 0x80242006

Working with some of my team mates this week, I was hearing about multiple machines failing the Fall Creators Update (FCU) 1709 with a Windows Update error of ” Feature update to Windows 10, version 1709 – Error 0x80242006 ” .  Looking around the internet I see a lot of people hitting the common solutions but no real success.

Common Solution (doesn’t always work)

  1. Run the Windows Update Troubleshooter
    1. Open the Windows Settings – Formerly known as the Control Panel
    2. Select Update & Security – Last option
    3. Select Troubleshoot – 4th one down left side
    4. Click on Windows Update under Windows.
    5. Click on Advanced on the Windows update dialog box and click on Run as administrator (Enter the credentials if required).
    6. Click on Next and follow onscreen instruction complete the Windows Update troubleshooter
  2. Deleting the %windir%\SoftwareDistribution folder (requires you to stop several services)

The two steps above only partially fixes the issue.  Solution is below!

Windows Update Log File

  1. Create the Windows Update Log file: Get-WindowsUpdateLog
    1. PowerShell Source: https://blogs.technet.microsoft.com/mniehaus/2017/10/10/improved-windows-update-log-formatting-with-windows-10-1709/
  2. Open the log file
    1. I still use cmtrace.exe as my primary log file viewer
      1. https://www.microsoft.com/en-us/download/details.aspx?id=50012
    2. I have found Glogg is much faster but less formatting
      1. http://glogg.bonnefon.org/download.html

Root Cause

You have at least two issues

  1. Partial download in the Software Distribution folder may be corrupted (someone rebooted for a reason)
  2. Real: You windows update agent registered a download but can’t clear it out

Solution

You need to stop services remove/rename two folders then restart services.  Please be aware cryptSvc will try to restart so do the following quick.

  1. Press Windows Key + X on the keyboard and then select “Command Prompt (Admin)” or “Windows PowerShell (Admin)” from the menu.
  2. Stop the following services in order Windows Update Services, Cryptographic, Background Intelligent Transfer Service (BITS), and MSI Installer.  The following command lines will work just fine.
net stop wuauserv
net stop cryptSvc
net Stop DoSvc
net stop bits
net stop msiserver

3. Rename the SoftwareDistribution and Catroot2 folders.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old

4. Now, let’s restart the BITS, Cryptographic, MSI Installer and the Windows Update Services.

net start msiserver
net start bits
net start DoSvc
net start cryptSvc
net start wuauserv

5. Rerun Windows Update to install FCU 1709

Notes

Media Creation Tool Fails

Media creation tool did not work in this environment because all clients are configured to be controlled via Microsoft System Center Configuration Manager (SCCM or ConfigMgr)

PowerShell

How to stop and start services

Get-Service BITS | Where {$_.status –eq 'Stopped'} |  Start-Service

Get-Service BITS | Where {$_.status –eq 'Running'} |  Stop-Service

How to rename a folder

Rename-Item -path 'C:\Windows\SoftwareDistribution' -NewName 'C:\Windows\SoftwareDistribution.old'

Rename-Item -path 'C:\Windows\catroot2' -NewName 'C:\Windows\catroot2.old'