Windows 1809 was released today during the Microsoft Surface hardware announcement today. Lots of progressive updates.
I will be posting more about 1809 features in the near future.
The most interesting note for me is that enterprises now have a 30 month window of support for fall releases. Yes, 30 months!
Enjoy downloading today!
Opened up Hyper-V today and all of my VMs where missing… umm what?
So I tried to connect to a server (button far right)
“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.”
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
Run the following command from an Elevated (Administrator) command prompt or PowerShell. Winkey+X >> Windows PowerShell (Admin)
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.
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:
- Click Start, and then click Run.
- In the Open box, type regedit, and then click OK.
- Locate and then click the following registry key:
- On the Edit menu, point to New, and then click DWORD Value.
- Type verbosestatus, and then press ENTER.
- Double-click the new key that you created, type
1 in the Value data box, and then click
- Quit Registry Editor.
Note Windows does not display status messages if the following key is present and the value is set to 1:
With this enabled I noticed I was having a long time with network configurations as it was running through the entire network stack history.
The easiest method to clear the history is to run the following command line:
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…
During the 1803 upgrade I noticed a new user logon status message I hadn’t seen before: Waiting for Workplace Connectivity. More research coming…
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
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
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
While at the 2018 MVP Summit I found from our own Brendan LeBlanc a wonderful website that tracks every single release of the Windows Insider builds. Great way to keep track of what’s new and whats trending