Slashdot Mirror

← Back to Stories (view on slashdot.org)

The Broken Design of Microsoft's "Fix it" Tool

Posted by kdawson on from the teething-problems dept.

$luggo writes "Curious about MS Fix It, I recently went hunting in the MS knowledge base for articles that provide the new EZ-button. After locating on few, I decided to click the button to download the Microsoft Installer package containing the executable and/or files that automatically enable the DVD Library feature in Windows Vista Home Premium and Ultimate — on my XP Media Center. 'Surely, MS will use some scripting, HTTP User-Agent sniffing, or even Genuine Windows validation to verify that I am running Vista,' I thought. It did not and I canceled the download when I received the prompt to save the file. So, I wonder: is there a Fix-it for Fix it? Because I can easily imagine someone doing what I did without scrolling to the bottom of the KB article and verifying that the article applies to their OS/version. This is a great example poor design. Why not simply use the download approach that other articles / fixes / service packs use, whereby the user must select the appropriate OS?"

1 of 165 comments (clear)

  1. Brain Repair by Spatial · · Score: 5, Funny

    Curious about Brain-Repair, I recently went hunting in the Slashdot Brain Repository for summaries that provide the new brain-repair-button. After locating on few [sic], I decided to click the button to download the Slashdot package to automatically enable the the Consider Actions feature in Idiot OS - on my brain.

    "Surely, Slashdot will use some pupil dilation measurements, phrenology, or even invasive surgery to verify that I do in fact have a brain," I thought. It did not and I stopped in my tracks when I received the prompt to read the study materials into my brain myself.

    So, I wonder: is there a repair button for Brain-Repair? Because I can easily imagine someone doing what I did without scrolling to the bottom of the Slashdot Brain Repository and verifying that the Consider Actions package applies to their brain. This is a great example poor design. [sic] Why not simply use the Brain Preview Jar approach that other Repositories use, whereby the user must select the appropriate brain?