Search This Blog

Here I will blog my daily efforts as a System Admin and hope that others will find answers here to problems that I already found the solutions for. I work with Hyper-V, DPM, SCCM, Office, Infopath, SQL Server, SQL Reporting Services, SharePoint, Windows Servers, Windows 10 and the 3CX PBX.

[SOLVED] Windows 10 Preview Build 9841 fails to upgrade to 9860

Today the first update to the Windows 10 preview came out.When I tried to upgrade I got this error:Failed to install the new preview build, please try again later. 0x80080005My Windows 10 install is an upgraded Windows 8.1 PC that was updated from Window 8 RTM. I have Visual Studio so I have many options turned on, like IIS. (Internet Information Server)I installed the x64 Enterprise version from the ISO download.This is the errors I got from the Event viewer after the upgrade failed 3 minutes into the upgrade:

Comments

Popular posts from this blog

It's that time again! Time to add your Office 2016 KMS Keys to your Volume Activation Server!Yes, I forgot how to do it too.. so here are my notes for doing it.

If you are missing the KMS keys from the MVLSC for office 2016 then you need to contact Microsoft at KMSADD@microsoft.com to get your MAK key converted to KMS.If you want to call them, use this number: (866) 230-0560 Here is the format of my email to them:

When you get your KMS keys, then you are ready to download the update from the Microsoft Volume Licensing Service Center (VLSC) that will allow you to activate the KMS on your Server. Look for "Office Professional Plus 2016 Key Management Servi…

I had a few Hyper-V 2012 R2 hosts that didn't want to talk to my VMM 2012 R2 server, so I started down the long road of tracking down the problems. Sorry if some of this seems disjointed or out of order. I'm trying to document this all after a week of troubleshooting errors.

Here is my advice for tracking down the problems. Most are related to WinRM.

Step 1: Check the Health status of the HostTo check the Health status of a host, perform the following steps: 1. Open the VMM Console.2. Select the Fabric view, right-click the host that’s experiencing issues and chose properties. 3. Within the host properties, select Status. 4. Select the category that has the Red exclamation to view the error details. In my case, the third category down was WinRM that was giving me an error.

Lets start with the easy stuff.Make sure WMI is working...net start winmgmtIf you think the WMI repository is corrupted, you could try this:winmgmt /salvagerepositoryThere is more detail on fixing WMI here:http:/…

2. Go to the Volume License Service Center and see if you already have KMS keys.If your using Server 2012 R2 (2008 R2 is not supported for Windows 10 KMS) you will need to get a KMS key called "Windows Srv 2012R2 DataCtr/Std KMS for Windows 10".In VLSC - click License, then Relationship Summary. Now click the License ID of your current Active license. Once the page changes, click Product Keys. Scroll down the list and look for "Windows Srv 2012R2 DataCtr/Std KMS for Windows 10" If you are missing the KMS keys from the MVLSC then you need to contact Microsoft at KMSADD@microsoft.com to get your MAK key converted to KMS.You will need 2012R2 with SA to get this Special KMS key.…