Posts tagged: windows 8

An End to Unwanted UAC prompts

By , May 25, 2014 7:29 am

We have just updated all of our software tools so that they no longer require administrator privileges to run. No more unwanted User Account Control prompts!

I’m going to explain why we used to require administrator privileges, why we’ve removed that requirement and what impacts that has for you the user of the software.

The past: Our software tools up until 24 May 2014


If you’ve ever used our tools on Windows Vista, Windows 7 or Windows 8 you’ll know that our tools required Administrator privileges to run.

Because of this each time you start the software you are faced with a User Account Control dialog. There is a pause, the screen darkens and then the User Account Control dialog is displayed. You can’t do anything other than interact with this dialog. It’s a “Yes I want to run this. No I don’t want to run this.” deal. But of course you want to run this software, you just started it. Hal really should open the pod bay doors.

This gets even more frustrating if you’ve used our command line interface to automate your testing or if you need the software under test to run without administrator privileges.


The ideal scenario would be for the software to run without requiring administrator privileges, just like most applications on your computer. This would improve the usability of the software, make automated testing smoother and just be better all around.

Reasons for change

When our tools require administrator rights to run there are multiple consequences of that requirement:


  1. A User Account Control dialog is displayed, interrupting the user’s flow.
  2. Automated tests require someone present to approve each tests’s run because a User Account Control dialog is displayed. This either partially or completely defeats the purpose of automating the tests.
  3. The software under test is now run with Administrator privileges. For most applications that isn’t an issue but for some applications this is not the correct privilege level for that application to run at.

The first issue isn’t ideal and adds frustration to the user’s life.

The second issue is horrible.

The third issue is a deal breaker for the few people that must test their application’s at a specific privilege level.

As you can see we had to change this state of affairs.

Working without Administrator Privileges

When running the software without administrator privileges the only thing you’ll notice is no administrator privileges. You can launch and monitor applications without administrator privileges. You can also monitor services that are linked to the NT Service API associated with the tool without administrator privileges. Only the Inject into Application and Wait For Application functionality (C++ tools only) prompt you for administrator privileges. Other than that the software works the same as usual.


If you run the software without administrator privileges the software will communicate with SVLAdminServiceX86 or SVLAdminServiceX64 as appropriate. The service will do the work required.

The C++ tools now work with desktop application, services running on LocalSystem account and services running on LocalService account.


You can still right click the software and run the software with administrator privileges. If you choose this the software will behave exactly as it did in the previous release, it will do all the actions itself and not ask the SVL Admin Service to do the work.

If you want to Inject into a running process or Wait for an application to start we can still do that with the C++ tools but you will need to run with administrator privileges to do that. This is principally because CreateRemoteThread from a service doesn’t work when the target application is not running in the same Windows session. This is a Windows security improvement. Until we can provide a workaround for this these two activities require administrator privileges. The software will automatically prompt you for this process elevation.

Similarly if you launch an application using CreateProcess (the recommended method) you don’t need administrator privileges. But if you choose any of the other options you will be prompted for administrator privileges.

Why did we require administrator privileges?

Our software tools are dynamic analysis tools that analyse the behaviour of software at runtime. As such our tools use a variety of techniques to invade the user space of the software under test and to communicate the collected data back to the user interface. If the software is a desktop application then different security environments are in force compared to if the software is a service. When dealing with a service such as Internet Information Server then you are dealing with a very locked down process. Some of these processes are very hard to interact with. You may be able to inject into the process but then not communicate with the user interface.

To cope with this early versions of our software simply used global shared memory (prefix the shared memory name with \Global) and ran with appropriate debug security privileges. This worked really well. Then came Vista with the new security regime. I’m sorry to say that our initial response was lazy. We simply put admin privileges on everything as a temporary workaround until we could get around to fixing things so they’d work without admin privileges.

So what happened? We got side tracked. We spent a lot of time focussing on other things, supporting different operating systems, different Visual Studio, porting the software to 64 bit, floating licences, improving the UX of tools like C++ Coverage Validator. And because we were at the time developing on Windows XP x64 we didn’t feel the pain of using the new security regime all the time. We’d use Windows 7 for our email machines, personal laptops and for testing but not for daily development.

Why were we using Windows XP x64? The answer is simple. The compressed start menu on Windows 7 is harder to use than the flyout menu on Windows XP. The search functionality on Windows XP is so much easier to use than that built into Windows 7, especially if you are searching for words inside a document (think Visual Studio project, manifest, source code, etc). Yes I know Windows 7 search has great power built into it, but it’s slow, hard to use as it’s crammed into one tiny window and in my experience often doesn’t work. Whereas the Windows XP search experience is simple, easy, reliable and fast (three fields, file name, content to search for, where to search). Sadly Microsoft has made search on Windows 8 even worse (right click on a search result and if you open the location you lose the search results – how is that useful?). And of course the start menu has gone.

Anyway, as the end date for Windows XP support, April 8th, loomed we started getting queries about our software that we’d never fielded before. Most were related to the User Account Control issues already described. People who had been using Windows XP and Windows XP x64 for development were abandoning ship, moving to Windows 7 or Windows 8. By the time we got to the start of March I knew we had to drop everything we were doing, annoy some of our existing customers by putting certain work on hold, and make our software run without administrator privileges. No User Account Dialogs!

Usually we issue one or two software releases per week. Or maybe one every two weeks. Our last software release was March 19th, over 10 weeks ago. This has been the longest break between software releases we’ve ever had. The scope of the work has been huge. We’ve had to write a service that the software talks to to do anything that would normally require administrator privileges. Then we had to identify every area that was impacted by the change in privilege levels. This meant some areas of the software had to be completely re-written. For example our Registry handling software now also has to be able to write to files and memory so that we can pass that data to the service so that the service can populate certains parts of the Registry on behalf of the software tool. Another area that has changed is shared memory. You can no longer just prefix everything with \Global and expect it to work. As such shared memory handling has had to change. This is particularly important if you are working with services. Copying files to certain locations is no longer possible. Writing files to certain locations is no longer possible. All these things we’ve had to address. We’ve had to update the installers to correctly install the service (and uninstall it first if we’re replacing it with an updated version). We’ve had to test on Windows XP, Windows x64 (to ensure our XP customers still get the experience they expect) and on Windows 7 and Windows 7 x64, Windows 8 to ensure everything works correctly. The different security handling for services between XP and Windows 7/8 causes some interesting problems to be worked around. We’ve tested everything to bits.

And along the way we’ve re-factored some of our software and also exposed and fixed some low level bugs in our hooking software (some of which are a side effect of recent optimisations in the way Microsoft build their operating system DLLs). Error reporting on the Diagnostic tab has improved.

Weren’t we dog-fooding?

You might think we weren’t dog-fooding. That is, using our own software to test our software. Yes, we do use our own tools.

But we were not using our tools in an environment that would cause these issues to be apparent to us. We had chosen to eat at our favourite restaurant rather than at the best restaurant in town. Having just spent two weeks on a cruise ship this analogy is sound, we quickly concluded that we preferred the Bistro over the fancy restaurant.

In fact we had deliberately chosen Windows XP x64 because we found it easier to use for the reasons already stated. In hindsight, although this was a good choice for ease of development it was a poor choice from the point of view of experiencing what the bleeding edge of our customers use.

Our new development environment

Our current development environment is Windows 7 but we’ll be moving to Windows 8 as soon as the new machines arrive. For Windows 8 we’ll be adding the Stardock Start8 Start menu. We’ve also written some search tools that although crude, allow us to search files more easily than using Windows 8 built in search functionality. We’re writing more tools to make our development work easier, even as Microsoft’s own UX efforts make what we want to do harder.


The move from administrator privileges required has been a time consuming, challenging experience. We’ve learned a lot along the way and had to change how our software works. However the result is that you, our customers, the users of our software now have an easier time using the software. I hope you agree the effort was worth it.

Microsoft Surface RT, my first month

By , February 1, 2013 6:16 pm


On the 1st January 2013 I purchased a Microsoft Surface RT. I purchased the 64GB version that comes with the touch cover. I didn’t purchase the expensive type cover. For those of you that are familiar with my experience with and comments regarding Windows 8 this should come as something of a surprise.

On the Windows 8 blog, on this blog and on the @softwareverify twitter feed I’ve been very critical of Windows 8, the lack of the start menu and how appalling the Metro user interface is on a desktop machine.

Ok, so given that I think Windows 8 desktop is a huge step backwards and I don’t like Metro on the desktop why would I spend money purchasing a Microsoft Surface RT tablet?

The reason I purchased a Surface RT is because I’d seen an early Microsoft tablet just after the Microsoft developer conference where they announced the Metro direction. I liked the tablet but I doubted they could make it work on the desktop. I was an early adopter of the Asus Transformer (a tablet that has a keyboard dock) and I thought it would be daft to miss the Surface experience. I don’t have an iPad, but I’ve seen plenty. My partner also has an iPad.

This won’t be an exhaustive review because that isn’t what I set out to do. I wanted to see if the Surface works for me. Many things that other people want from a tablet I probably don’t care about and I probably care about things that others don’t.

If you want a more in-depth review, try this another I’ve had a Surface for a month review. All of which I pretty much agree with.


The build quality is superb. I much prefer it to my partner’s iPad (4th generation). The case is tough, light and not flimsy at all. The 22′ tilt provided by the kick stand works well. It’s not going to be perfect for all uses, but works well on a desk, which it was probably intended for.

The USB port is great for plugging peripherals in. I tried a USB powered DVD drive which I normally use with my x86 netbook. The Surface recognised it instantly and allowed me to read the DVD with no problems at all, from both Metro and the Desktop.

The screen is fantastic. Yes, I know it doesn’t have the resolution of the latest iPad. Frankly, if you’re looking at it you can’t tell. The screen construction techniques mean the screen is better than the iPad screen and combine that with Microsoft’s font rendering technology and you’ve got an excellent experience. Couple that with viewing angles to die for and you’ve got a really nice experience. You can watch video from really oblique angles and still see the action with no colour distortion, unlike any other computer (any OS, any vendor) I’ve seen.

The keyboard attaches to the Surface via single magnetic connector. The magnetic keyboard attachment is solid and clunks into place with a firm snap, first time, every time. Fold the keyboard under the Surface and the screen keyboard takes over. The keyboard, although thin and part of the cover works just fine. I prefer it to the keyboard on my Asus Transformer.

When you type, either on the keyboard or the screen keyboard each key has it’s own audio sound played via the speakers. The keys are divided into groups, so letters have one sound, navigation keys another, delete and return another etc. This is very useful and adds to the UX. You very quickly get useful feedback for how your typing is going. The sounds are not unique though so someone can’t audibly eavesdrop on your typing.

The built in mousepad works well enough. Surprisingly good considering the size of it and the form factor.


Battery life is excellent. On standby it seems to last forever, unlike my Asus Transformer. In use I seem to get a day or more out of it between charges. Can’t fault it. Does what it says on the tin.

Power adapter

I don’t like the power adapter. Microsoft have been too clever here. It’s a magnetic power adapter. It can be attached either way around. It would have been good if the manual had said that. The first time I went to charge the Surface I had to search the web to check it was safe to plug in either way around. The last thing you want to do is throw £559 away just because you plugged it in the wrong way around.

Plugging it in can be awkward. Most times it just attaches and starts charging but occasionally it can be finicky and just won’t connect. And no matter how hard you push it won’t connect. You have to disconnect and then try again. Doesn’t happen often but when it does it can be very annoying and waste a bit of time. I’m not fat fingered. I play mandolin and bagpipe. I am dextrous. This isn’t a problem of a clumsy user. It’s a problem of a not quite right power adapter.

And once you have it plugged in how do you tell if it’s charging? Well the obvious place would be a charging led on the Surface itself. This is standard convention on mobile phones, all other tablets, laptops, netbooks, etc. Typically two or three colours (low, medium, full charge). The Surface? Not a chance. No leds on the Surface. The charging led is on the end of the power adapter next to the magnetic attachment. Which means until you notice it you won’t see it, especially if you’ve oriented the power adapter to face down (if you have it on the kickstand when you are charging). In my case, I again resorted to the web to check if there was a charging led, finally found it. Multi-colour? Nope. Just white.

I also don’t like that the charging led is not on the Surface because what if there is a problem with the attachment such that the led illuminates but it doesn’t charge the Surface? If the led was on the Surface you’d know for sure that power was getting through. As it is you just have to trust that the cable is OK and that the Surface is charging.

Summary: Fiddly attachment. Led in wrong place. Led should be bi-colour or tri-colour. Far too clever for their own good.

User Experience, Metro

The Metro user experience is superb. Metro with a touch screen just works. The various slide in from the side operations and left-right-left to reveal the running tasks is so easy to learn. It seems very natural when you do it with touch. I much prefer this to Android or iOS. You can also kill any running Metro application by simply sliding from the top to the bottom of the screen. Simple, easy, efficient.

I also like that when you swipe from the right it displays the charms bar on the right (search, settings, etc) and also the time and battery life on the left. Any running application keeps running. So you can do this in the middle of a live streaming broadcast to get a quick idea of the time then swipe to the right to dismiss it. Two swipes with a minor pause between and you’ve just seen the time. Really simple and easy.

When you drop out of a Metro app it effectively stops running. Go back to it and it’s running. This works brilliantly with applications such as Netflix which instantly restart. Even if you put it into standby then bring it out of standby, it restarts, which in the case of Netflix is a brilliant user experience.

Internet explorer is a great user experience with Metro, the various swipes/slides working together really well. I particularly like the ability to pin a web page to the Start Screen. I’ve pinned BBC iPlayer, The Times, The Guardian, The Economist, various technology blogs, Business of Software video page, etc to the Start Screen and then moved all the pinned tiles into logical groups. Very, very nice touch.

I didn’t even bother using the Desktop version of Internet Explorer. Why would I bother when the Metro experience is so good?

I think putting the “go forward” navigation button on the right handside of the display is a blunder. I always look to the left to locate this. It should be on the left of the navigation bar, to the right of the “go backward” button. Just like in every other browser. The fact it’s a tablet doesn’t change this. I lose more time looking for the button that I would possibly save by having it under my right thumb. Yeah, people navigate by thinking which thumb a button is under? Really?


Flash support is better than for say the iPad but not as good as the Asus Transformer (an Android tablet), in that some websites can display Flash content (for example WordPress and YouTube), but others cannot (Channel Five television – a UK channel). Why not? Who knows. This is just sheer stupidity on Microsoft’s part. There is no value to be gained and much to be lost by banning support Flash from arbitrary websites. So if I want to catch up with something Channel 5 show I have to use my PC or my Android tablet. How daft is that? I’m going to watch it anyway, so let me watch it on my Surface.

Mail, People, Skydrive

I haven’t really had a need for these, so can’t comment on them.

I found the Maps application to be useful. It seems to match Google Maps for the tasks I need.


The app store works. People complain that there are only 25,000 applications in the store. Do you really have time to choose from that many applications? The fact that iOS/Android have more is simply an I’m bigger than you contest. It’s meaningless. What matters is are there apps you can use and are they of good enough quality? So far I’ve been able to find apps to do what I want and yes they’ve been OK, some have been excellent. This can only get better over time.

I downloaded apps from Amazon, Kindle, Ebay, Netflix, TeamViewer, RemoteDesktop, MetroTwit, The Economist, etc. No problem with these.

When downloading an application rather than having an “it’s working” indicator it would be useful and sensible to have a progress bar so you can see how long it is taking to download the software. Both Android and iOS have this. Surface doesn’t.

I also found that the Store would often fail to download an application, or would say it had lost it’s connection to the Internet far too easily (when you checked the ‘net was always there). This marred the store experience on occasion.

Killing Apps

Occasionally you’ll find an application is misbehaving. This is easy to solve. Simply swipe from top of screen to bottom. The app is killed. Simply restart from the start screen.

On two occasions, once after configuring the WiFi and once after some software updates I found the networking would not work. Simply rebooting (or powering down then back on) resolved the problem. Interestingly you find the power button is under settings. In Windows 8 on a desktop this seems (and is) nonsensical. However for a tablet this works nicely – keeping a dangerous action like this hidden away from accidental triggering.

User Experience, Desktop

The desktop experience, as with Windows 8, is still appalling. It doesn’t work well with touch. And without a Start Menu you are lost as you can’t find anything with a mouse. So then you are stuck with the Start Screen, which for working with the desktop is a waste of space. You lose your context when you switch to the start screen from the desktop. Search results are gone when you go back to it from the desktop. It’s broken.

And worse than that because you can’t load your own ARM compiled applications you are stuck to doing whatever you can do with the version of Microsoft Office that comes pre-installed. I don’t have a use for office. For me I’d like to install a couple of my own applications compiled for ARM and possibly a non-Metro email client (Thunderbird, again compiled for ARM).

Frankly without a start menu to get quick and easy access to the programs I want it’s too hard to use. The Start Screen is just a hopeless way to work with the desktop:

  • Go to search, then find Apps, then scroll right, then hunt around until you find the icon, if you are lucky enough to have that program listed.

  • Type the name of the program, assuming you know the proper name of the program.

The first method is painfully slow. The second method requires me to remember the names of lots of programs I don’t know the names of. I just know the human readable name and the desktop icon. Trivially easy from the desktop and start menu. Slow, tedious, error prone or impossible using Metro.

The good folks over at XDA-Developers have worked out a hack that will allow you to load and run ARM compiled binaries on the Surface RT.

The main problem is I don’t want (or need) to learn a new desktop working behaviour when I already have one that is very efficient. The Windows 8 method is really slow, labourious and actively gets in my way. This will never work. Microsoft would do better to realise that the Desktop and Metro are two separate ways of working and they should modify things to allow Desktop users to work in ways that are effective for the desktop without imposing Metro on them. And vice-versa for Metro users.

Do I like the Surface RT?

Yes. Very much. Despite my criticisms this is an excellent tablet. Microsoft have made some stupid decisions, mainly for ill advised market segmentation reasons, to do with the desktop. But I didn’t buy it for the desktop. I expected the desktop to be unusable without the start menu and I was right. I bought it for the tablet experience, which is excellent.

I’ve had my Asus Transformer since it was launched. I use it occasionally, but the not so good standby time and the dreadfully short charging cable meant that I pretty much left it in one place in the house. My Surface RT however gets carried all over the place, it’s thinner, lighter, better screen, better UX.

Should I have purchased an iPad 4th gen? No, I don’t think so. My partner has one of those and she is happy with it. But I prefer the UX on the Surface RT (if we put the desktop abomination to one side, seeing as the iPad doesn’t have that anyway).


So there you have it. I still hate the Windows 8 Desktop experience that forces me fight Metro. But when using the Surface as tablet I love Metro. Metro just does not and never will work well with a mouse. Just don’t even waste your time trying.

This is a wasted opportunity for Microsoft. Great hardware marred by stupid software decisions.

People want a full day battery life tablet. The Surface RT is that.

Microsoft should stop with the stupid marketing tricks and allow side loading of ARM compiled Desktop applications on the Surface RT. Then business customers could have a full day tablet that can do their work. The Surface Pro doesn’t provide this.

Microsoft need to sort out their marketing. So far it’s been so bad it’s been invisible.

If my experience with the Surface RT is anything to go by the Surface Pro will be a hit. Shame about the battery life.

Things to fix:

  • Start menu on the desktop.

  • Allow ARM compiled applications on the desktop.

  • Flash support for all websites.

  • Power led.

  • Power adapter.

  • Stop trying to shoehorn desktop users into the same paradigm as Metro (for any version of Windows 8, Surface or PC). It doesn’t work.

Windows 8 Start Screen disaster

By , October 13, 2011 11:19 am

Over on the MSDN blog there is a series of articles about Windows 8. Among those articles are three articles about the Windows 8 Start Screen which replaces the Start Menu.

Some background

I’ve been a member of MSDN since late 1994 when I first heard about MSJ magazine and then heard about MSDN. I’ve worked with Microsoft technologies for the vast majority of the time since then and pretty much exclusively since 1998. I’ve hated the backwards steps the Start menu took from Windows XP to Windows Vista/7 but the Windows 8 process – well that is such a change that I think this will debut so badly that this will be worse than the reception Vista received.

The Vista machines we purchased we got rid of. We have Vista as virtual machines only. We do like Windows 7 though. That works.

So far, despite repeated trials of Windows 8, all I can say is that it is awful. It is not productive, not for how we work. I don’t care how good it is at touch or how well it does web related home-consumer tasks. None of that helps me be productive in my day job. That is what counts. It is, more importantly, also what counts for my customers.

I want Windows 8 to be a success. That is why I am pushing back so hard against the Windows 8 start screen.

MSDN Blog articles

The first article Evolving the Start menu explains what they did and why they did it. It received a lot of negative criticism. They followed up with a second article Designing the Start screen which completely ignored all the criticism and tried to steamroller the Start Screen as superb. This duly received a lot of further criticism.

There is now a third article Reflecting your comments on the Start screen which is full of information, insights and analysis on how they came to arrive at the Start screen and why they think the Start menu should go away. The problem is the arguments are not convincing.

Menus are inefficient

The first argument is that the Start menu is inefficient. That it requires dextrous control of the mouse to find and select an item (this is true) and that it is slow to do so (also, reasonably true).

Therefore they introduce the start screen which is a 2 dimensional grid of tiles that you can easily find with your mouse etc. The problem is, this is not true. They boast that on screens of 1900 x 1080 resolution you can have 80 tiles.

Whooppee! Er No.

I have a screen of 1900 x 1200 and it has 72 icons on the desktop. Can I easily find the icon I want to launch a program? Yes, sometimes. But most of the time I have to scan the whole thing to find the one I want. And I organised that group of icons. It is not efficient. Sometimes despite knowing what I want is in my list of 72 icons I can’t find it and I give up and go and find it from the Search menu anyway.

And Microsoft want all of us to work this way in future. Yikes!

And of couse when you can’t find it you then have to use the new Search functionality. Which I’ll tell you about now…


The old Start menu had a search function on it. In Windows 2000 and Windows XP this was really efficient – you could tell it where to search, what to look for in a document all before starting the search. No time wasted.

In Windows Vista and Windows 7 this was awful, very inefficient. You had to start a search you knew would fail, then bring up the search widget, choose custom and flail around in that awful user interface then get the search (with no progress indicator showing which directory was getting searched – we had that in W2K and XP).

The new Windows 8 search function – there isn’t one. Wait, there is. Just its invisible. Which is why I didn’t know it exists. Its that discoverable that an MSDN member of 17 years could not find it.

Yes, I know I know, I must be an old fart, but seriously. If I can’t find it can my parents, can my girlfriend, can the people working in the Vetinary surgery down the road? No they can’t.

To use search in Windows 8 you have to switch to the start screen and then type. That’s right type into nothing, just type. Apparently this nonesense is inspired from mobile phones. Thats great. Except it isn’t. I’m happy with that metaphor on a phone. But I want my PC to behave like a PC. What is efficient for one device is not efficient for another. If that were true we’d control aircraft the same way we control submarines. Unsurprisingly we don’t.

Furthermore when you switch to the Start menu to make your search you lose the context of your work – so god help you if were hoping to read some text from a website or a document to type into the search widget. How efficient is that? They just made you add an extra step – you now have to copy and paste the text from the website or document. What? The text isn’t copy and pastable? Oh dear, no you’ve got to copy the text off the document onto some paper, switch to the Start screen and then type what you’ve written on paper into the invisible search widget.

Sound exaggerated? Perhaps. But I can see this happening. Especially with less au-fait users like the aforementioned people at the Vetinary surgery (I am actually thinking of some people I know – good with animals, not so with computers – just things to use, on the Desktop!).

But I don’t know what I’m looking for

You don’t know what you’re looking for? So how will you know when you find it? Well, I can kind of remember its name, but not really, but I’ll know it when I see it.

Its like being in a library in the philosophy section and you’re not sure what you’re looking for then all of a sudden you hit the section of Thoreau books and out pops the one you’re looking for. How could I have forgotten its name? Silly me.

Well indeed. And its the same with programs. Often I can’t remember who wrote it (so I can’t select by Vendor) or what its exact name is. My developer machine has 94 menus on the Programs section and most of those have submenus with between 5 and 10 items on. Some have more and some have more submenus. That is a lot of program names to rememeber. Unsurprisingly I don’t rememeber them. I have better things to devote my memory to. But I can browse those menus relatively easily and with reasonable speed.

The main reason I can do that, browse between 450 and 900 items is because each menu only exposes the data under it when I look at it. If I had to look at all 450-900 items at once it would impossible. Most of the items I never look at the submenus, I just have to read the main menu entry and then move on or occasionally check the contents.

It is an efficient compromise between having to use search to search for all executables and then dig through the ridiculous number of results (very slow) and the other extreme where I have to remember them all.

The problem with Windows 8 is that there is no Start menu to browse. I have to use search to find what I want. How can I find what I want when I don’t know its name? Answers on a postcard please (or leave them in the comments section).

Live Updates

A few of the comments in support of Metro in the MSDN blog comments indicate that the poster of these comments thinks that people with views like mine are dinosaurs that can’t see the value of having updating live tiles. What a limited and narrow view.

Such live tiles were previewed in Vista with the gadgets on the screen. Sure they are useful. I haven’t said they are not useful. I have said I don’t wish to work that way. These are different concerns just as some people wish to drive manual cars and others don’t want that chore so they choose an automatic car. In fact that is not a bad analogy, Metro would be the automatic car (less control) and Start Menu users would be driving a manual car (more control).

I have no need for an email tile keeping me up to date with my email. Why? Because I work with 2 computers and three screens. One computer is dedicated to handling email and browsing the web. The other one is for development work. The email machine has an email browser open all the time. Even if I had one machine I’d have the email client open all the time. An email tile is a waste of CPU time for me.

Also, if you know anything about productivity the last thing you want is a screenful of animated tiles doing their thing in your peripheral vision. Nice eye candy for the easily impressed. Boring annoyance for those of us that want to get stuff done.

Ubuntu One

Linux? Who cares about Linux? Why suddenly talk about Linux?

Well they’ve already done this particular experiment for you. The most recent release of Ubuntu comes with the Ubuntu One interface as the default. This is a user interface that makes you access everything via tiles (admittedly more restricted than Metro) and forces you to work with single screen applications.

I first tried it on my netbook. My initial thoughts were that it was good. Web browser and email clients come up full screen (all 800×600 of it!) and I could browse the web OK.

Then a few weeks later I thought I’d install Ruby On Rails on it and take a toy project away with me for a bit of tinkering while on a break. What a disaster. Totally impossible to get anything done in these single whole-screen environments. I spent a good deal of my time in the task switcher moving one window to the front, finding another, then moving that to the front and so on.

That installation of Ubuntu got replaced with the standard Ubuntu classic and all future installations are setup deliberately to exlude Ubuntu One. If you read around the web you’ll find lots of power users also hate Ubuntu One. Just like the power users complaining on the MSDN blog about Metro. You’re taking control (and thus productivity) away from your best customers.


The Windows 8 Start Screen covers all your screens. Not user friendly at all. Completely stops any context. As far as I am concerned losing even one whole screen is way too much, especially when you consider how efficient and non-context losing the start menu is.

If the start screen could be encompassed in a resizable window so you could move it whereever you want, or minimize it out of the way that would be useful. This in addition of course, to actually having a proper functioning start menu.


Many complaints have been made about the inability to kill tasks in the Metro interface (all you can do is suspend them). Also the lack of support for multi-tasking windows is a real productivity killer.

These complaints remain un-addressed by the Windows 8 developer team.

No Compromise

The Windows 8 developer team seem completely unconcerned that those of us that want to use their PC to do work do not wish to work in a fashion that is dictated by the needs and desires of those whose only use for a PC is to consume the web/youtube/facebook/email on their tablet or gaming PC.

Both groups of people can be accomodated.

  • Business users. Leave our Windows Desktop alone and give us the Start menu we know and love.
  • Home users. By all means give them the tablet UI you have designed Metro for.

Why can’t this be a configurable option? A powerful Start menu option for folks like myself and the Metro interface for people that think search is a useful replacement for the Start menu.

User Experience

The user experience that I have had with Windows 8 Developer Preview has been extremely poor. Open source operating systems like Haiku give you a better experience out of the box.

Dog Food

I really do wonder if the Windows 8 Developer team is using Windows 8 to develop Windows 8. And I mean everyone, the management team, everyone that has to use office, powerpoint, email, MS Project, all the development team, including people using WinDbg and Visual Studio. I can’t believe they are because the loss in productivity would be huge.

I have to conclude the only people eating the Windows 8 dog food are the home consumer testing group that want a tablet/phone/home-user user interface.


I hope that having read this far you realise that the problem with Windows 8 Start Screen is not the start screen itself. It is the drop in productivity and the horrible context switch from Desktop to Start Screen (which itself is a productivity issue) that are the issues. We know what is productive for us. And, although you think you know best for us Microsoft, you don’t.

I’ve already experienced Windows Vista/7 search and hate it. I don’t want to have to use Windows 8 search even more than I already have to use Windows 7 search.

Keep search as what it is good for and allow me to browse for my files, productively, using the Start menu.

Windows 8 #fail

I hope that when Windows 8 finally debuts people can look back at this article and think “Thank God, it didn’t happen, Windows 8 is still productive”.

Otherwise we’ll all be walking around in T-Shirts with the slogan “Windows 8 #fail”.

Panorama Theme by Themocracy