Quarter Five – Thoughts and Solutions
The Idea is to Observe, Discover, Ponder, Propose, and Do.
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) POPUP ERROR 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
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.
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
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
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 https://flighthub.azurewebsites.net/
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. There are no files to be sync’d and it just constantly states processing changes. I have seen a few threads online stating this may be due
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
Congratulations! Thank you for your continued contributions to the Windows community, we are excited to re-award you as a Windows Insider MVP. This award is a token of our appreciation, your leadership and passion help make Windows the best yet. We look forward to our on-going collaboration with you and all of our Windows Insider
I frequently benefit from Microsoft Sysinternals tools like Process Explorer (ProcExp64.exe). One of the features is the ability to replace the Task Manager Default with Process explorer. However, I found a bug. If you use the x64 version of Process Explorer to change the default you can’t change it back!?!? Solution: You have to open
Hello all, In the past month I have done 3 separate talks about the new release of Windows 10 FCU (1709). The link below is the slides from the last talk: CTSMUG201710 – Fall Creators Update 1709 The 5 links below are the most useful but I call out a lot of good data below.
