Why all this fussing over builds is meaningless

posted on July 15, 2009 by Bryant Zadegan

RTM! A few days ago, Long famously proclaimed that build 7600.16384 would be RTM (now retracted). Since then, another build has been compiled, and WZOR claims that this new build, 7600.16385, would be RTM. With this back-and-forth and soon-to-be-short-lived debate over which build will be released to manufacturing, I felt the need to drop by and remind people of a few things:

  1. RTM isn’t just this magical thing which is compiled and then immediately signed off. It takes roughly a week’s worth of testing (in the Windows world. Shane Nokes, who happens to have experience elsewhere, knows that Microsoft could sign a project off after only three days) before certifying that a build is worthy of RTM.
  2. 7600 will be RTM. Stop worrying about which compile of 7600 will be RTM; they only have very minor changes, if anything at all.
  3. There’s nothing new in these last few builds. There’s no new theme, no new components… nothing. What’s the point of worrying about which build is compiled if there’s literally no visible difference?

Of course, there’s much more to my little OP/ED here after the jump, so be cool and get to it.

Read More »

Windows 7 Anytime Upgrade boxing hands-on (exc)

posted on June 25, 2009 by Bryant Zadegan

Update: Please, if you’re going to copy my images, don’t delete the watermark. I went through effort to get these pictures, and having them torn off (as is the case with ArsTechnica’s recent linkback)just means that I’ll have to present unsightly watermarks over the entire picture next time as opposed to keeping the images presentable by leaving the watermark in the corner. Update 2: ArsTechnica corrected their image accordingly. Thanks!

Just about everyone has seen the shots of the new Windows 7 retail packaging, but pictures of the new Anytime Upgrade packaging are much harder to come by. Impossible to find are any current examples of the packaging besides press shots and renders, so having said that, here are a few good hands-on shots I managed to take. For those wondering, yes, this means the boxes themselves are real, and that yes, Microsoft will indeed be pushing Anytime Upgrade through retail channels.

If you want some context as to how Microsoft arrived to this new box design, go ahead and check out Brandon LeBlanc’s post over at the Windows Team Blog. As for a physical size comparison: the full version boxes carry the same dimensions as the current Vista boxes.

(There’s nothing relevant inside the boxes themselves; just a fake key and a CD of Visio inside the retail box of which I was also taking some pictures.)

Have at it:

Retail Ultimate v. Anytime Upgrade UltimateInside boxes exposedBusiness AU v. Ultimate AUBusiness AU v. Ultimate AU side by sideBusiness AU v. Ultimate AU perspective shotBusiness AU v. Ultimate AU lower shot

On an unrelated note, we (the staff of AeroXperience) would like to wish our condolences to the Jackson family with regards to the recent, sudden, and highly tragic passing of Michael Jackson

If you’re running 7077, please upgrade to 7100

posted on April 25, 2009 by Bryant Zadegan

win7small Seems a few people have been pushing around the idea that 7077 is no different from 7100. Given that 7088 was the build that was jumped to 7100 and not 7077, it means there were still 11 builds worth of changes before a build was finally signed off as the release candidate for Windows 7.

If you’re running Windows 7 build 7077 (leaked earlier), you really do need to install 7100 if you want to give any relevant feedback. 7077 still has a few stability issues which, if reported, would be nothing more than a waste of time while being totally redundant. Granted, the build is stable, but when you’ve got a more stable build available to you, why hold back?

As everyone knows, 7100 already leaked via usenet/torrents, but if you want to give feedback, your best bet would be to just wait until 7100 is released via the usual channels (in this case, MSDN/TechNet on April 30 and worldwide on May 5).

Sorry for singling you out, Ed. You’re awesome, but I had to post this to suppress any confusion which might’ve resulted amongst our readers from your post.

Welcome to Windows (Mobile?) 7

posted on February 11, 2009 by Tony

Tin-foil hats on! This article, though based on factual information, is 100% pure speculation!

We all know the story. Windows Mobile 7 has been delayed time and again. For the Windows Mobile team, that’s usually par for the course: WinMo releases have typically been few and far apart, and that was OK. But as of late, Microsoft has not only received tough competition, but has been absolutely trounced in the Smartphone market by RIM, Apple, Google and soon a resurgent Palm. Par isn’t going to cut it anymore. To keep up with the big boys, Microsoft is gonna have to step up its game.

Oh sure, they’ve got some interesting things coming down the pipe: My Phone, Skymarket, Zune Mobile; but does anyone really imagine that these services will stop the exodus? Microsoft needs to do something big, and I think (hope?) they’re already on it.

The picture above is from (one of) Microsoft’s Windows 7 site(s). If you take a quick look at the red arrow, you’ll see Windows 7’s beta wallpaper on a Smartphone. What could that mean?

Now, it could be entirely innocent and mundane (it probably is, but where’s the fun in that?). Maybe Microsoft is implying that Windows 7 and Windows Mobile just Work Better Together™.

I happen to think it’s pointing to an as-of-yet unannounced version of Windows 7 – Windows 7 Mobile/Phone/Cute-Marketing-Word-Here.

When I first heard about MinWin, I imagined that Microsoft was pushing to slice and dice Windows into smaller and smaller pieces so it could build a phone-optimized version of their desktop OS, a la Apple and OSX. Then at D6, we got word that Windows 7 would support multi-touch, which, while only moderately useful on laptops (and gimmicky on desktops), makes a ton of sense for a phone. PDC gave us even more info on features that make oh-so-much sense on phones, including Location awareness, a sensor platform (accelerometer and proximity sensors anyone?), and OS-level support for connecting to 3G networks.

Then, just last week, we get this quote from Motorola’s CEO:

“…more of our effort and focus in 2009 is going to Android, but in 2010 when Windows 7 will become available, we will then participate in a more focused way in Windows Mobile 7 in 2010″ – Sanjay Jha, CEO, Motorola

I’m not one for conspiracy theories, but the amount of evidence for this hypothesis is surprising, and Microsoft desperately needs to overhaul Windows Mobile in order to compete against Apple’s iPhone and Palm’s webOS. And they very well could be. Perhaps the WinMo7 delays are Microsoft retooling, shifting from the struggling Windows CE ancestry to the more robust Windows kernel for Windows Mobile 7.

Will Windows 7 be the underpinnings for the next version of Windows Mobile? Even though Windows Mobile 6.5 is being foreseen as the hot topic next week, maybe we’ll still get some sort of answer on Windows Mobile 7.

Windows 7 SKU Hell? Yes, but no.

posted on February 6, 2009 by Devin

Three days ago, the internet received reports that Windows 7 would ship in six versions, but that it would only be available at retail in three flavors: Home Premium, Professional, and Ultimate (limited in quantity). The bigger news was in how these SKUs would work. All versions of Windows 7 are tiered – whatever features are available in a certain editon are also available in each successive editon.

Let’s take a look at the changes between editions of Windows 7 and Windows Vista as well as the guys who blew this whole non-issue completely out of proportion. We’ll help clear up the air and show Microsoft’s plans for Windows 7 as the understandable gig it always was. Catch the highly critical and immensely interesting read after the jump.

Read More »

UAC in 7: Exponential Silent Attack Vector Multiplier

posted on February 4, 2009 by Bryant Zadegan

badUAC

(Update: official statement appended to the end of the post)

I’m going to open this post by kindly asking you, the user, to go into the Windows 7 Action Center (Control Panel, System and Security, Action Center), clicking “Change User Account Control settings” and setting it to the maximum setting (“Always notify me when…”).

The reason for why I’m asking you to do this shouldn’t be a surprise. You may have seen the UAC posts by Rafael Rivera and Long Zheng (I’m giving more of the credit to Rafael since he actually brewed the proof of concept code). People saw their posts and immediately assumed that this issue is only relevant for users who download malware. Thus, you hear lots of users saying out loud with no apparent fear of embarrassment:

“La di da, so long as I’m not stupid with what I download, I should be fine!”

Right. Well, Microsoft basically recommends for users to install an antivirus because they don’t actually consider User Account Control to be a security feature. Anyone who knows the purpose of privilege management knows that any system which actively manages privileges is a security feature.

With this in mind, let’s take a look at why the UAC security flaw actually is a security flaw.

Update 2: Steven and Jon posted a second post about UAC today specifically addressing this flaw. Catch their response below the break.

Read More »

Why Windows 7’s CEIP bug shouldn’t have happened

posted on January 19, 2009 by Bryant Zadegan

When an application or operating system in beta crashes, it’s expected. Typical beta testers don’t throw a fit about failing beta applications; instead, they file bugs to the appropriate teams handling the parts of the program(s) which failed. This is standard procedure (at least with those used to Quality Assurance).

On the other hand, the systems which are not supposed to crash are the ones which are associated with bug reporting, user experience improvement, et cetera. So, when said utilities crash, what do you do?

Chris Holmes, a mutual friend of mine and Rafael, recently discovered (along with Rafael) the source of a round of interesting crashes in Windows 7 Beta 1. The bug itself is uninteresting and typical; besides crashing virtually anything running on top of a Windows service which calls the SQM client (a part of the CEIP), it’s nothing big. What interests me the most is that this bug is triggered when the Customer Experience Improvement Program is running.

Catch my abnormally detailed reasoning after the break.

Update: The Windows Team pushed a nicer solution to the Action Center. The solution may need to be re-used every once in a while as disabled sessions accumulate, but it’s better than killing the CEIP outright. Catch more at the end of the post.

Read More »

The release of Beta 1: a missed opportunity

posted on January 10, 2009 by Bryant Zadegan

bad7 Microsoft tossed Windows 7 Beta 1 live for public consumption yesterday. Unfortunately, inadequate planning led to servers which they were using for the release (likely hosted by Akamai, though it would look even worse if Microsoft hosted the bits directly) to collapse under pressure at least twice. This is an IT headache which, sadly, came at a terrible time for those involved (Lisa, don’t lay them off just over one mistake!)

However, this situation could have been handled in two far better ways. The first possibility would have been the bit torrent protocol. Given the ubiquity of torrent clients, this would have been a great way to get the bits into peoples’ hands fast. However, given that bit torrent is, unfortunately, automatically associated with piracy, Microsoft may have felt that using it would have legitimized the protocol’s existence, thus causing “problems” down the road for their anti-piracy teams.

Thus, bit torrent usage for distribution of Windows 7 Beta 1 would have been a Very Bad Thing™. However, this doesn’t mean Microsoft didn’t have another far more tantalizing tool up their sleeves. Keep in mind that Microsoft needed a

  1. cost effective
  2. internet scalable
  3. very fast file distribution solution

for distributing Beta 1.

Enter Avalanche. Let’s do a quick take on the first paragraph of Avalanche’s description, shall we?

The code-named research project “Avalanche” studies how to enable a cost effective, internet scalable and very fast file distribution solution (e.g. for TV on-demand, patches, software distribution). Such an approach leverages desktop PCs to aid in the distribution process, relieving congested servers and network links from most of the traffic.

Right. Obviously, Akamai, identified in part thanks to the wonders of 20/20 hindsight, hasn’t served its role as a “cost effective, internet scalable, very fast file distribution solution.” Avalanche, on the other hand (assuming proper implementation), would have worked perfectly given that Microsoft would have had a few “peers” online to kickstart the distribution (a fraction of the Akamai capacity it asked for). This was one of those times where Microsoft had a shot at implementing something absolutely wonderful but skipped on doing so for… well, nothing’s sake really.

Implementing Avalanche would have posed a solid number of benefits for Microsoft:

  1. A new protocol and application would have seen mass deployment across a solid number of computers.
  2. Microsoft would have reinforced their desired image as an “innovator” (using bit torrent has its benefits, but it’s hardly considered secure. The largest benefit to Avalanche is that peers have “zero-information of who has what,” which is certainly an innovation in its own right given the lack of privacy with the bit torrent protocol).
  3. Windows 7 Beta 1 would have been handed off to those wanting a copy far faster than the current direct download solution.

Maybe it was the piracy stigma associated with p2p technology, but a quick rewording of how Avalanche works would have solved this in the public eye.

In the end, it just seems as if Microsoft blew a great shot.

Update: Stebet points out that Avalanche did leave whitepaper status for the distribution of Visual Studio 2008 Beta 2, but it seems the client is no longer available for download.

Regionalized Themes in Windows 7

posted on December 6, 2008 by Bryant Zadegan

Build 6956 was leaked to the public yesterday in the form of a virtual hard drive. Those who got it running probably didn’t take the time to dig deep, but our own Michael Frank took a look inside the build to see what he could find.

Right on par with some of the changes I mentioned would be coming to Windows 7, regional themes are now an option for different countries. It’s expected that more will be added as time goes on, but the five English-speaking countries currently stereotyped themed in build 6956+ are:

  • Australia
  • Canada
  • South Africa
  • United Kingdom
  • United States

The themes are nothing more than color and wallpaper combinations for now. I’m assuming that the appropriate theme will be chosen depending on the location of the person installing Windows 7, but that has yet to be seen.

Beta 1 is currently in escrow, so any other remaining hidden features should also be visible by the time Beta 1 rolls around on January 13th at the MSDN Developer Conferences*. We should have more information for you guys regarding these themes down the road, but for now, feel free to check out screenshots of the five country-specific themes below:

 

AustraliaCanadaSouth AfricaUnited KingdomUnited States

*if any of you are attending the MSDN DevCon in Washington D.C., I’ll gladly meet up with you at the event! Just drop me a PM on the forums in advance to arrange a meeting place.

Windows 7 Error Recovery actually works!

posted on December 2, 2008 by Bryant Zadegan

I got to work today and booted my macbook. Having forgotten that I switched it to boot Windows the night before, I didn’t hold the Option key to boot into Mac OS 10.5 (for work needs. I wouldn’t dare keep it otherwise). I wasn’t paying much attention to what was going on with the screen as I was in the middle of a meeting, but I got back to it after about 5 minutes and came upon the above scene unfolding on my laptop. It was vaguely familiar; Paul Thurrott reminded me later that it’s an offshoot of the Windows Recovery Environment which is now integrated into Windows 7 as opposed to being contained solely on the installation DVD.

The fact that the Windows Recovery Environment (WinRE) would be contained in the Windows 7 installation is nothing new; reviewers covered this after their reviews went live on Windows 7 keynote day at PDC. However, no one has actually seen it work, so here I am.

Yes, it actually works.

In my case, my instance of build 6801 died on an “unknown bugcheck: 12b” which led to WinRE being launched. The recovery mechanism checked for issues, subsequently asked me if I’d like to use system restore to roll back to the last working point, rolled back, and presented me with full details of all of its scans (some of which you’ll see in my quick-n-dirty BlackBerry shots). After all of that, it rebooted and voila, Windows 7!

I didn’t lose Rafael’s BlueBadging either, though Rafael did lose his mind over how irritating this feature might become for techs.

Catch the remaining three pics after the break, and feel free to leave your thoughts on whether you think this will or will not be useful to home users, nerd users, sysadmins, etc.

If you’re with the Windows Error Reporting team, please check your error reports for this one. 4th pic contains the most relevant information.

Read More »