Windows 7 just overtook XP in the United States

Windows 7 just overtook XP in the United States

Posted in Main on April 8th, 2011 by Pingdom

Microsoft WindowsIt’s finally happened. After a long reign at the top, Microsoft’s Windows XP is no longer the most widely used desktop operating system in the United States, instead turning the crown over to Windows 7.

As of April, Windows 7 has 31.71% of the desktop operating system market, compared to 31.56% for Windows XP.

Here is the current distribution of desktop operating systems in the United States, based on the first seven days of April:

Desktop OS market share, United States, April 2011

The data is from StatCounter and consists of aggregated visitor stats from more than three million websites. In other words, this reflects the market share distribution of computers used to access the Web.

The rapid rise of Windows 7 has been a massive success after Microsoft’s relative failure with Windows Vista (which never got the upper hand on XP). Since its launch in October 2009, the rise of Windows 7 has been straight as an arrow.

Desktop OS market share over time, United States

Windows XP is still a big presence, especially in the corporate space where many have resisted upgrading, but Windows 7 seems to finally have set the upgrade train rolling.

What about the rest of the world?

Worldwide, Windows 7 has a market share of 31.17%, while Windows XP still holds a significant 46.87% (now in April).

However, this doesn’t mean the United States is the only country where Windows 7 has overtaken Windows XP. There are actually a number of countries where this has already happened, sometimes several months ago. A few examples:

  • United Kingdom
  • Canada
  • Australia
  • France
  • Germany
  • Belgium
  • Denmark
  • Finland
  • Netherlands
  • Norway
  • Sweden

So in this sense, the United States actually turns out to be a bit behind the curve.

Posted in News For Small Business Admins, Win7, XP. Comments Off on Windows 7 just overtook XP in the United States »

Update: What you need to know about Windows 7 Service Pack 1

Repost of

Windows 7 Service Pack 1 has been out for a month. Here’s a quick list of the known problems that warrant your attention

By Woody Leonhard | InfoWorld
<!– document.writeln('’); // –>

What you need to know about Windows 7 Service Pack 1
If you’ve been waiting to install Windows 7 SP1 on your users’ machines or hesitating about installing SP1 on your own PC, you might want to wait a little bit longer. There have been a few — remarkably few — identified problems with the Service Pack and some additional unconfirmed reports that warrant your attention. Here’s what you need to know.

Microsoft’s TechNet blogs contain detailed explanations of a handful of identified, fully dissected problems. In particular:

The Remote Server Administration Tools don’t work with SP1. If you need RSAT, it’s safest to simply hold off on installing SP1, although there’s a work-around posted on the TechNet site. Microsoft promises a fix next month. The RSAT tools have been implicated in failed SP1 installations with error code 0x800f081f.

TechNet has detailed instructions for coping with installation failures with these error codes: 0x800f0a12, 0x8004a029, 0x800f0a13 or 0x800f0826, 0x800f0904, and 0xC000022. The causes range from obscure Registry settings to a third-party utility to wayward antivirus products. There’s another error on installation, 0xC0000034, that hasn’t been nailed down as yet; it seems to be quite rare, though, and it (or an error just like it) also afflicts Windows Vista. There appear to be open questions about errors 0x80004005 and 0xC000009A. TechNet even has an admonition about running SP1 on Windows 7 systems that have most or all of the Language Packs installed.

( Update: Microsoft has changed the Windows Server Update Services (WSUS) package, as described in KB 894199. The KB article notes, simply, that SP1 “Packages have been updated to address a known issue. Packages have changed, but binaries have not changed.” In other words, SP1 itself hasn’t been changed, but the installer has. In typical Microsoft fashion, there’s no indication of specifically what has been changed or why, but conjecture among the cognoscenti is that Microsoft may have finally figured out how to fix the 0xC0000034 bug. Before you install SP1 using WSUS, check the new thread on 0xC0000034 to see if there’s any breaking news on the “torn state.” Thanks to Susan Bradley for the heads-up.)

Microsoft also has a list of application programs that have problems with SP1, in Knowledge Base article KB 2492938.

Those are the well-known issues. I’ve heard from several people who tried to install SP1 and encountered a smorgasbord of problems. Usually, disabling security software, updating the system BIOS, or replacing the hard drive knocked things loose.

One reported problem continues to bother me. I’ve had several people write to say that after installing SP1 their machines booted much slower than they used to. The advice offered by Microsoft is to reboot the machine five times and try again. Five boots are necessary to reset the ReadyBoot RAM cache. That advice has worked for some of the victims, but not in all cases. The mystery continues.

Bottom line: Windows 7 SP1 has rolled out exceptionally well. (Almost certainly a big part of the success of the rollout is due to the fact that Windows 7 SP1 doesn’t do much.) If you haven’t yet installed SP1 on your company’s Windows 7 PCs, it’s time to start thinking about it.

This article, “What you need to know about Windows 7 Service Pack 1,” was originally published at Get the first word on what the important tech news really means with the InfoWorld Tech Watch blog. For the latest business technology news, follow on Twitter.


Posted in Win7. Comments Off on Update: What you need to know about Windows 7 Service Pack 1 »

Media Player doesn’t start in IE8 When Clicking on Links containing .avi, asf, ,wmv, mpg, mpeg,

When I moved to Win7 I noticed that any Links that contained a URL with
.wmv, mpg, mpeg, avi,

Why I didn’t have a clue I did some looking and I found this answer:
>>>>>>>>>>>Microsoft Answer was. <<<<<<<<<<<<<<
To resolve this behavior, reregister the Wmpdxm.dll file.
To do this, follow these steps:
1.At a command prompt, type one of the following commands:
2.At a command prompt, type the following command:
regsvr32.exe wmpdxm.dll
3.Start Registry Editor. Verify that the following registry key points to the correct path and file name for the (Default) value:
Typically, the registry key points to the following path and file name:
 >>>>>> End of Microsoft Answer <<<<<<<<

However I found that didn’t work
Looking around I found a post from Charles_Flook

And he suggested this which worked.

Open up notepad.exe
past the below into notepad and save as a MediaPlayerFix.reg file and open.
(allow it to make the changes)

>>>>>>>>>> MediaPlayerFix.reg <<<<<<<<<<<<<
Windows Registry Editor Version 5.00

>>>>>>>>>>>>>>>>>> End <<<<<<<<<<<<<<<

Then any links that end in the .avi, asf, ,wmv, mpg, mpeg, wiill open media Player.
Thanks Charles_Flook

Posted in IE8, Win7. Comments Off on Media Player doesn’t start in IE8 When Clicking on Links containing .avi, asf, ,wmv, mpg, mpeg, »

PDF Handler for Vista not working in outlook 2007 on Win7 64bit

I found this fix from Leo Davidson,
for PDF Handler not working in Outlook 2007 on Win7 64bit and it Works Great!

Frome Source Page

Download Fix

Alternate Download: (Without permission from Leo)

Thanks Leo 🙂

Posted in 64bit, Outlook2007, Win7. Comments Off on PDF Handler for Vista not working in outlook 2007 on Win7 64bit »