Shortly after I published my Regardless of what any hack says, a Windows 7 Upgrade is an Upgrade. What you need to know blog post, there was one particular statement that several people seemed to focus on. The statement in that blog post I am referring to is, “Over the past several days there have been various posts, etc. across a variety of social media engines stating that some “hack” shows that a Windows 7 Upgrade disc can perform a “clean” installation of Windows 7 on a blank drive from a technical perspective.” Shortly thereafter, many came to the conclusion that the “hack” was a person and began speculating (and even some actually going so far as stating as “fact”) who the “hack” is that I was referring to in that post.
As promised in my Answers from Windows 7 Upgrade Install Hack post coming on Monday post from this weekend, here is the post where I will reveal the identity of the “hack” that I was referring to in that post. This is one of the many answers to questions I am putting up on the blog throughout today and the week. As those of you that have followed my Blog for some time know, a lot of the posts here are based on questions I receive and topics of concern I see in the Partner community.
After my Regardless of what any hack says, a Windows 7 Upgrade is an Upgrade. What you need to know blog post, there were a couple things I observed (and these are all important factors in how we got here and in the revealing of the “hacks” identity):
Let’s start with the “conspiracy-theorism.” One theme that came up in several of the comments posted to my blog post, other blog posts, and other articles that came about from my blog post was, “Microsoft tries to make it hard for their customers/Partners,” or “Microsoft does not care about trying to help their customers/Partners be successful.” Really? I can assure you with 100% certainty that Microsoft is absolutely committed to working to improve the satisfaction and experience of all of our customers and Partners, which is the entire reason that the Customer and Partner Experience (CPE) effort that I left my former position at Microsoft to join in 2008 exists. Now does this mean that Microsoft has mastered all parts of it and that everything is rosy? Of course not (and no, contrary to several of the comments posted, I am not that blind to think they are). But know this, improving Microsoft’s customer and Partner satisfaction is a long-term, on-going journey that we are absolutely 100% committed to taking with you. Here are just two specific examples of this:
Now about those “pre-determined conclusion” lenses… It seems very apparent that many people commenting on my post, either directly on it or on any of the articles about it, figured they knew what it said even before reading it and/or did not completely read it before drawing their final conclusions or making their comments.
Just one example:
So let’s get down to identifying the “hack,” I was referring to.
The “hack” is Ed Bott! Really? No, not really, regardless of how many people tried to convince you of that by making that claim since my post. In fact, just the fact that people implied that Ed Bott even could have been the person I was talking about shows that people did not read my post before jumping to their conclusions about what it was saying or they had their “pre-determined conclusion” lenses on when they did read it. As I said above, in my blog post I stated, “If the posts or write-ups you saw did include this information about needing the full license to upgrade from), then kudos to that writer for providing the accurate information.” Did you read Ed Bott’s post? If you had, you would have seen that Ed clearly states in his answer to the question, “So, does this mean I can install an upgrade version on a new PC I’m building?” Answer: “From a technical point of view, yes. But from a licensing point of view, absolutely not. The discounted price for an upgrade applies because you already paid for a license on the system you’re upgrading.”
Not only is Ed Bott not the “hack” mentioned in my post, but he is actually an example of what TO DO when posting information about this type of a workaround for clients. And this isn’t the first time Ed has done this either. How many of you read his, “The Vista license "loophole" that isn't,” post when this same issue arose about the double-install method with the Windows Vista upgrade media? Once again in that post, Ed calls out, “If you qualify for an upgrade license, this technique allows you to do a clean install, legally. If you don’t qualify for an upgrade license, then doing a clean install with this technique is technically possible but violates the terms of the license agreement.” He goes on even further to explain this to his readers. Personally, I would suggest that people posting about technical workarounds in the future, regardless of who they are, take a page from Ed Bott’s book of how to do it.
Ok, so if Ed Bott is not the “hack” I was referring to, then it must by Paul Thurrott! Really? No, not really. What did Paul Thurrott post that was factually inaccurate, intentionally misleading, or anything else that you would expect from a “hack”? Haven’t seen his post yet? Read it here. Paul does a step-by-step explanation in his post about how to execute the clean install and nowhere in the post does he tell people that this alleviates the need to be buy a full license of Windows 7 just because it works (unlike some others in the past, and currently have done). In fact, Paul, like Ed, is one of the people that many people have pointed to over the years as being one of the very helpful people in pointing out solutions to technical issues discovered.
Based on all of the speculation and cases of “opinionasfactitis” (pronounced: Opinion-as-fact-itis. You know, where someone states an opinion as a “fact” and then that “fact” continues to propagate as a “fact” like a contagious disease, in this case articles in tech publications/forums stating my post was calling out Paul directly), floating around, Paul obviously is/was of the opinion that I felt he was condoning piracy in his post or that I was stating he should not have published the information in his post based on his follow-up post.
In my opinion, no, Paul’s post is not condoning piracy and as stated above, nowhere have I said that either Ed’s or Paul’s posts shouldn’t be published or are condoning piracy. Yes, I do believe it would be beneficial if Paul had specifically called out in his post that this workaround does not alleviate the licensing requirements of the upgrade so that readers do not mistake his helpful post to be stating something to the contrary. Especially since there have been numerous comments on various blogs/forums and even articles written using Paul’s post as the “source” of this tip to get around the need to buy a full Windows license if you don’t qualify for the upgrade. So my only feedback on Paul’s original post is, would you mind including the quick few statements like Ed in your posts to eliminate all confusion on whether your post eliminates the need to be licensed properly so that these other people do not misinterpret your information that way? Because to answer the question posed in his follow-up post, while you would think that the line in the EULA that states, “To use upgrade software, you must first be licensed for the software that is eligible for the upgrade” that he quoted in that post would be obvious to understand, based on all of the comments and feedback of people stating the contrary about their impressions as they make their arguments, apparently it is not.
Before moving on, let me set the record straight. Ed and Paul, if either of you felt that my post from last week was implying that either of you are “hacks” or publicly condoning piracy, you have my sincere apologies here on public record, as in no way was that my intention. (In full disclosure, Ed and I did have a chance to connect directly on this over the weekend already; however, Paul and I have not)
So wait a minute… If Ed and Paul are not the “hacks” called out in the post, who is? Is it this guy that was listed by another online tech magazine as the target of my post? No, not him; however, I really do appreciate him going back and adding the following to his write-up just afterwards:
“Update: While it is not necessary to buy a full version of Windows 7 it is still a legal requirement to do so if you do not own a legal copy of either Windows XP or Windows Vista. The article did not make that completely clear.”
So then who is it? The “hack” I am specifically calling out in my post isn’t a “who,” it’s a “what.” A “what” you ask? Yes, a “what.” Take a look at the definition of “hack” in the Merriam-Webster Dictionary. (I know, because I did before my original post to ensure the wording I was using was accurate).
The “hack” is any of the technical workarounds you see floating around (not any one in particular, it can be any of them out there that exist today or that come out in the future) that state that the Windows upgrade can physically be installed as a full product. Because let’s be clear, just as the title of my blog post says, “Regardless of what any hack (technical workaround) says, a Windows 7 Upgrade is an Upgrade.” And just like I have been saying for years, “Technically possible” does not always mean legal, so just because you “can” do it, that does not change any of the licensing terms or requirements. Just make sure you have the proper licenses first, as Ed Bott pointed out in his write-ups. Then as I said in my original post, “there are many, many, many, many of you out there that already own Windows licenses that qualify for the Windows 7 Upgrade, so this is a non-issue for you. That’s also why I called out that there are things you need to know (and those would be the licensing requirements listed in my original post).
So for anyone out there thinking my post was trying to “make an example” of someone as a “hack” or that I was calling someone specifically a “hack,” sorry to disappoint you. As I mentioned in the very beginning of this post, I have no doubt that “conspiracy-theorism” and “pre-determined conclusion” lenses had a lot to do with people coming to that conclusion. (Not to mention the “Opionionasfactitis” that was spreading rampantly) In all honesty, looking back, how many of you actually read my original blog post without any pre-determined notions as to what you already thought I was going to say, just because I chose the word “hack” in it vs. “technical workaround?” And those that had pre-existing notions of what I was going to say, how many of those were positive? People see the word, “hack,” mentioned by someone at Microsoft and quickly start to assume the negative side of it. Why?
As I said above, contrary to any beliefs out there, Microsoft is 100% committed to working with all of our customers and Partners to increase your satisfaction with our products and company. We know there are issues that need to be worked on and we are committed to working on them with you. For those of you that I have worked with for years, as I have always committed to doing in the past, I will continue to work to provide information and answers to address questions and concerns I see being raised and will continue to try to point you to where you can find the RIGHT answers to those questions. But to be clear, the RIGHT answer is not always the POPULAR answer; however, just giving the popular answer, if it is wrong, does no one any good anyway. Just like people trying to twist the solutions stated by Ed and Paul, that were designed to help address a technical challenge, to convince customers as being legal ways to “cheat the system,” does not change the real answer that an Upgrade is an Upgrade and you need a qualifying license to upgrade from. Whether I put up my post or not, the upgrade licensing requirements remain the same. But if putting up my post helped protect some customers from being told the wrong information by someone or helped clear up the questions for some of our Partners out there that service the needs of their customers on how this works, then it has served its purpose.
Also, after reading through the comments that I have seen on my blog post and in many of the articles and other publications on this topic, there are a few common themes I have been seeing that people seem most concerned with. Because of this, I will be putting up another post this week entitled, “Eric, I am soooo mad at you because” where I will try to address many of the themes and help answer and address these concerns, and some of them are very valid and very legit.
Note: One comment that continues to come up is that I am “avoiding” answering Microsoft’s procedure for the install. I guarantee you I am not avoiding it. I have submitted your various comments on this topic to the appropriate people for that topic and will be happy (believe me) to post the exact link to where you should go for this information as soon as I hear back.
As I noted over the weekend, I am going to be posting the answers to many of the questions I have received and continue to receive here on the Blog, so please keep the feedback and input coming. You can see many of these questions and answers posted here:
More Answers from Windows 7 Upgrade Install Hack post
Thank you and have a wonderful day,
Eric Ligman – Follow me on TWITTER and RSS Global Partner Experience Lead Microsoft Worldwide Partner Group This posting is provided "AS IS" with no warranties, and confers no rights
@ MV and Dan Hallock - I have taken the feedback submitted to me on this and forwarded it to the appropriate people. I will let you know what I hear back.
I have to say after reading both of your blog entries and both of Paul T's on this subject, you have far more patience than me and should be commended. For Paul to put up the blog he did on Monday claiming you are backpedaling (which I don't think you are or should be after reading this) and then take shots at you even after you tried to contact him and openly apologized is just wrong. At this point I think it is Paul that should be putting up the apology.