Weekend Scripter: A Week's Worth of Windows 10


Summary: Ed Wilson, Microsoft Scripting Guy, talks more about his first impressions of Windows 10.

Microsoft Scripting Guy, Ed Wilson, is here. I will admit that I am not a typical user—of anything, as far as that goes, but certainly not of desktop operating systems. So my thoughts about Windows 10 may or may not, be relevant.

First of all, I can say that I have been “using” Windows 10 for about a year because I get the daily builds. But this is not all that true because installing Windows 10 and immediately launching Windows PowerShell hardly counts as using Windows 10. So in reality, my only real experience has been this past week.

I have two experiences to report:

  1. I did a complete fresh installation on my laptop. The reason for this is, well, I am old school, and always believe that a fresh installation of Windows is a good thing. In fact, in the Windows 95 days, I did a complete reinstall every three months. Your mileage may vary.
  2. I let Windows Update do the upgrade on my beloved Surface Pro 3. This device is my favorite device, and I was halfway intending to keep it running Windows 8.1 for a while. But I have Windows 8.1 running on my Surface Pro 2, which is also a great device, so I figured I could risk it.

Fresh install versus Windows Update

Because I have been installing Windows 10 nearly every day for a year, I did not think about it too much. I logged on to MSDN, downloaded the ISE, burned it to a DVD, and fought with my laptop to get it to boot off of the DVD. I mean, Windows 8.1 boots so quickly that there is little time for pressing F1, or F2, F10, or F12, holding down ESC, or whatever other secret combination a laptop maker tends to dream up for whatever current model they are shipping.

My Surface Pro 3 was easy. I clicked the pop-up balloon, and it started.

I finally got the laptop to boot off of the DVD, typed in the key, and it was off to the races. Oh yeah, at some point, I told it to wipe out my existing partitions and go from there.

Note  Prior to doing any upgrade, it is always an excellent idea to perform a data backup. This is especially important if you intend to delete your existing partitions, reformat the drives, and do a fresh installation.

When the installation began on both devices, the Scripting Wife and I headed to the library and out for dinner. When we returned, there was a simple prompt on both devices. I answered a question or two and it was done.

After installing/upgrading, now what?

After the fresh installation on my laptop, I had to search around for a few minutes to find where we had hidden Windows Update because there are always security updates and bug fixes. I found it at:

Windows flag > Settings > Update and Security > Windows Update

I forced it to check for updates, and then did this a couple more times. I installed Office 2013 and checked for more updates. This time, it did not seem to find anything, but I know there are lots of Office updates that need to be applied. I then remembered that Windows Update on Windows 10 likes to run in the background and do everything itself. So I left my laptop on and checked back the next morning.

Upgrade results

On my Windows Surface Pro 3, things were streamlined. I already had Office 2013 installed in addition to a bunch of apps. So following the upgrade, everything was seamless. I did not have to do any new installing. I clicked my Facebook app, and I was able to immediately make posts. I clicked the new Windows 10 Mail app, and my online email account immediately worked. Unfortunately, it lost the settings for a different legacy email server. That was rather annoying, and it required some time to fix.

My biggest shock on my Surface Pro 3 was that it went immediately into “Desktop mode,” and the Start screen (which I love on a mobile surface device) was basically gone. I did a few searches on the Internet trying to figure this out (I remembered that Windows 10 was supposed to detect the type of device and switch “modes” on the fly.

I guess, this means that with the keyboard attached (95 percent of the time, I keep my keyboard installed because it folds back and makes a nice stable platform for using the device in “Tablet mode.” Unfortunately, I never did find the correct answer for how to switch modes. I finally stumbled across it in the settings. It is really easy to switch modes:

Windows flag > Settings > System > Tablet mode

Then I clicked Make Windows more touch-friendly when using your device as a tablet and When I sign In. Then I selected Automatically Switch to Tablet Mode.

That is it. I guess all of the “bad advice” I found on the Internet was applicable to earlier beta versions of Windows 10.

By the way, the “touch mode” is disabled if your device (such as an old laptop) is not touch-enabled.

So I can say that the upgrade on my Windows Surface Pro 3 has been flawless. I mean, really, it went perfectly. It kept my installed apps, remembered 99% of my settings, and has worked perfectly. On my laptop, I have had to reinstall everything—including existing apps that I had previously owned. This is actually a little surprising, because when I installed Windows 8.1 and signed in with my online Microsoft account, it remembered which apps I had and reconstituted my Start screen. I miss that.

And of course, Windows PowerShell 5.0 in Windows 10 is awesome. All in all, this has been a great week. It is like a birthday week for a geek with new toys coming every day as I discover more reasons to love Windows 10. It is like all new devices.

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at scripter@microsoft.com, or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.

Ed Wilson, Microsoft Scripting Guy 

Comments (3)

  1. U&0 says:

    Reviews of the history and culture, I was just a couple of weeks ago.

  2. Niels de Groot says:

    Switching to tabletmode is easy. Click actioncenter in the taskbar, and click on the tabletmode button.

  3. Slogmeister Extraordinaire says:

    Failing to get the Office Updates after forcing a check does not seem flawless to me. It sounds like a huge security flaw. Giving false information that there are no additional updates leads users into believing that they are fully secure and ready to
    use their computer. Like many, I depend on Windows Update to deliver accurate and current information about updates and patches, particularly those related to security. Considering the behavior of most users and the danger of the suite of exploits that currently
    exist, this seems to me to be a terrible disservice to users and a major compromise to security best practices. Regarding Office, there are hundreds of security updates for it and having to wait 24 (or even 12) hours for your computer to be fully secure and
    ready to use is profoundly inconvenient (another mark against "flawless"). Additionally, a false update report for Office updates erodes my confidence in the accuracy of the report for the operating system’s updates. After all, both are Microsoft products
    and I would expect Microsoft to be aware of the state of their software. I am extremely concerned that you weren’t able to successfully secure the computer during the manual process and had to wait for the background processes (over which you have little or
    no control). Ed, I know that you’re often very much the optimist and cheerleader, but I think "flawless" is a bit strong here.

Skip to main content