We couldn’t install Windows 10; 0x8007002C–0x4000D

I was seeing the same damned error (“We couldn’t install Windows 10”; 0x8007002C–0x4000D The Installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation) on all four of my systems that I was trying to upgrade.

Microsoft may be changing a lot and trying to do better, but they’re NEVER going to succeed as long as they continue to maintain the mentality that error codes are a good thing.  I wouldn’t actually mind them if they provided a widely published and constantly updated database of what each and every Error code means.   But they don’t publish these codes widely, instead they only publish the one that a million people are complaining about.  And each new Error Code is as cryptic as the last.

Take the error code I mentioned previously:

WP_20150731_11_49_02_Pro“We couldn’t install Windows 10”
The Installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation.

The error was noted while Upgrading Windows 7 Ultimate to Windows 10 Pro.  The upgrade process would get to somewhere in the 83% to 85% range and would then go to a blank screen, no warnings or errors.  It would sit there for approximately 50 minutes until the system would just spontaneously reboot, with subsequent boot screen messages indicating that Windows was reverting to the previous Operating System, or something to that extent.

It turns out that what they really mean is to do the following prior to beginning the process:

1.) Uninstall any third party Firewall/Security and AntiVirus/AntiMalware software you might be using.
2.) After removing software, reboot your computer to ensure a fresh start.

After removing AVAST Business Antivirus (it’s really a great A/V solution, can’t beat that it’s free!). AVAST had some additional cleanup that required a reboot, so I elected to “do the reboot later” and then I also removed Malwarebyte’s AntiMalware (also a really great A/M solution, and is also free!). 

I then restarted each computer and then restarted the Upgrade Process, and then went back to playing a game to kill time while it re-downloaded everything all over again. 


Two other aspects that I should probably mention, as they could have some impact on your results:

1.) I was using the Microsoft Media Creation Tool to launch my upgrade process. 
2.) I started it by right-clicking on the file and selecting “Run as Administrator” just to be safe.

This time, each of the four systems ran to completion, and successfully installed Windows 10, so I can call this a success.  The fact that the error message never once spoke of this particular issue in all of my research proves that Microsoft really needs to start working on those error messages, for everyone’s sake (and sanity).

Best of luck in your Upgrading efforts!

The topic of Net Neutrality revisited…

I wanted to take the time to communicate to you the single most important action that you need to take to retain your existing rights to free speech, but may not even have know about until you read this article.

Currently in front of the FCC is a proposal for changing of the current definition of Net Neutrality.  The FCC has issued a 120 Day Comment period, which has been extended recently due to the incredible influx of community comments so far.  The new deadline is September 15th.

Continue reading

When you can’t Connect HP Version Control Agent (VCA) to the Version Control Repository Manager (VCRM).

As a self-taught Systems Administrator, I tend to learn by the process of trial and error.  And boy have I erred a lot recently.  I’ve been banging my head against this particular brick wall (not being able to connect the HP VCA to the HP VCRM) in earnest the last couple of weeks:

HP VCA Connect

It seemed that no matter how I input the info on the screen above, the two would never see each other.  Credentials were confirmed, permissions vetted, yet every time I filled out this screen and clicked “next”, I would inevitably get the message “The specified repository, servername.domainname.com, is invalid or not reachable.”. I was just going around and around, in a downward spiral that didn’t bode well for my sanity.

I was therefore EXTREMELY happy when I found this gem in the HP Systems Insight Manager Support forums in a post talking about an upgrade from version to

I’ve got answer form HP TS regarding HP VCA working with HP VCRM

I did not got full answer of root cause of this issue but form provided command I suspect that it is is realted with SSL Cipher configuration.

For me these commands solved th issue.

Please try run follwing commands on server with HP VCRM


C:\HP\hpsmh\bin>smhconfig.exe -r

For me these commands solved the issue.


Sadly, I wasn’t sure this would resolve my problems, since I had never been able to get VCA and VCRM to talk initially, therefore my problems obviously were not due to an upgrade like everyone else’s.  However, some of the connectivity issues mirrored those I was experiencing, so I applied the fix as a batch-file (copy/paste commands to text file to avoid fat-fingering any characters, saved as .BAT file, issued command line “run as administrator”), and voila!  Suddenly I can connect the two together!   

Sadly, I have no breakdown of the intimate details involved with what the commands do exactly, or how they accomplish the resolution, but it was made clear that the problem was due to an SSL Cipher configuration.  My take is that it appears that HP had actually removed some expected ciphers from 7.3.x.x of VCRM, which then prevented the communication from VCA Agents.

But, all good now!

Microsoft begins offering WP7 “pre” Update

On Monday February 21st Microsoft began making a “pre-update” update available for Windows Phone devices.  The updates appeared to be distributed based on who the customer used as their wireless provider.  

Monday’s updates seemed to begin in some European countries, and some of the updates in North America were thru Rogers in Canada.

Make sure your WP7 device is configured to receive Updates (Settings > Phone Update > enable both) and make sure you are using v4.7 of Zune client software on your PC and Mac.  Mac users will also need the Connector software here or from the Mac App Store.

Please understand that the update will rolled-out in staggered fashion, so some users may have to wait a day or two before getting their update notification.

If you have problems installing the Update, please check out this Knowledgebase Article.   If you continue to have problems, please post a thread in the Windows Phone 7  forum at Microsoft Answers.

Day 1 of MVP Summit

Had a wonderful first Summit day today.  Attended a couple of optional “side sessions”, then attended the main Welcome Dinner hosted by Nestor Portillo (Director of Community & Online Support), standing-in for Steve Ballmer.  Poor Nestor was about as scared as I would be addressing such a large audience, but he held it together.  Good job!

Landed in Seattle for MVP Summit 2010

I landed in Seattle earlier this morning, and I am so looking forward to seeing all of my fellow MVP peers and my friends at Microsoft.  

My fellow MVP Moderators were also thrown a wonderful Welcome Dinner at Maggiano’s Little Italy in Bellvue, courtesy of Microsoft’s Windows Phone Forum Management Team.   THANK  YOU!!!

Bought my tickets for the 2010 MVP Summit

My hotel reservations were secured a few weeks ago, and I just recently bought my plane tickets, so I’m basically ready to go (minus packing a few days before the flight).

Having missed CES (Consumer Electronics Show) 2010, I am totally bummed to have also missed CntrStg 2010.   I really miss the interaction with my MVP peers and fellow bloggers, so the 2010 MVP Summit will be a great opportunity to meet new MVPs, connect with old friends, and enjoy the best that Microsoft has to offer!