As a Community Moderator on the Microsoft Surface Forums, it’s pretty easy for me to pick up trending hot issues (unlike the paid Forum staff who do not triage or correlate). I regularly forward these on to a contact inside Microsoft. At the end of June, I saw an increasing number of reports about a sudden and dramatic decrease in Surface Pro 3 battery capacity. I’ve been forwarding these along every since, asking that Microsoft at minimum state that “we are investigating reports”, but no official MS rep has even posted that they are reading and investigating.
Sadly, once out of warranty, it costs $99 to even contact official support. And the scripted answer is “we will replace your device with a refurb for $450” (etc.). Many folks have gone this route.
I’ve been scraping the forum and doing my own analysis. The folks who know how to run a battery report (admin cmd prompt, then powercfg /batteryreport) have been posting screen shots or cut and paste text outputs. Based on the sampling, I see only SIMPLO batteries and no LGC batteries. This is disturbing.
I’ve been begging MS to respond to afflicted users. The silence is deafening.
Below is a sampling of what I am scraping from the Forum. If you have a Surface Pro3 and are seeing diminished capacity, PLEASE post in http://answers.microsoft.com/en-us/surface/forum/surfpro3-surfhardware/surface-pro-3-battery-degradation/783f6a00-19ba-4dcf-a828-0ad87751e15a. Please include a screenshot/capture of the capacity history and the manufacturer of the battery.
You read the title correctly. I’ve added a fingerprint reader to my Surface 3. (And you can do this with any Windows 10 device that has a USB port). Windows Hello is a wonderful feature that provides an extra level of protection from prying eyes while traveling. While I’m not necessarily paranoid, I don’t want strangers seeing my password or PIN while I’m lunching and computing. I feel more secure.
While you can purchase a typecover for the Surface Pro 4 (that also works with Surface Pro 3, but this combo has some power management issues), there is no similar option to purchase a typecover with a fingerprint reader for a Surface 3.
Luckily, there’s a way to do this (if you don’t mind using the single USB port on the Surface 3 and tying it up at least while you log in; you can remove and attach this peripheral while Windows is running so for me it is no big deal).
Amazon sells this super tiny add-on fingerprint reader from “Eikon” at a good price. It’s made by Authentech, who made many of the built in fingerprint readers for nearly all the big computer vendors (they were purchased by Apple in 2012).
I attached this device to my Surface 3 (green arrow below) and Windows immediately recognized this device and installed what it needed (red arrow) in a few seconds.
I’m currently using Windows 10 Insider Build 14388, but this device will also set up in a similar manner on Windows 10 10586.xxx.
1. Go to Sign in options in Settings.
2. If you don’t already have a PIN, set one up as this is required to use a fingerprint reader.
3. Windows Hello will change the Require sign-in to Every Time as part of the setup and you will see this when setup is completed.
4. Next, you will need to “enroll” or setup at least one fingerprint; select Get started to launch the wizard.
5. Confirm your PIN when prompted.
6. Follow the prompts to swipe a finger and setup the first fingerprint (and add additional fingers if you wish to do so).
When complete, you’ll be able to log in using Windows Hello.
This is a neat little device and it installs and sets up seamlessly and flawlessly. I recommend it highly.
If you have any questions on this, you can contact me on Twitter @barbbowman or in the Microsoft Surface and Windows/Windows Insider Forums.
There has been a lot of misinformation in the Insider’s Forum (from customers) about the necessary free space to install an Insider’s Build. I decided to take my only low memory device, an ASUS Vivo Tab 8 M81C-B1-MSBK Signature Edition Tablet that I purchased from the Microsoft Store, and test this out for myself. The device is 32GB to start with and was VERY full. A little over 4GB free space was available. Nevertheless, I was able to install an Insiders Build from a mounted ISO and subsequently download and install the latest Fast Ring Insider’s Build from Windows Update.
Here’s how I did all of this:
I used the following procedure to install 14372 from an ISO image. This is the process that should work for folks upgrading from 10586.xxx 1511 to the official release of the Windows Anniversary Update (with a few changes on where and how to get the ISO) with minimal free space.
The first problem is that the default Downloads folder was on C:\ and only a bit over 4GB of free space was available, so I needed to move Downloads to my 128GB microSD card. I wanted to move this at the System level as opposed to just specifying a different folder. The ISO for 32 bit Windows is 3GB+ and to say the least, with only 4+ free, I needed to download to a drive other than C:\.
The process to move the folder is to right click/tap and hold the Downloads Folder and then select Properties, then the Location tab.
Then, select the Move button.
Then, navigate to the alternate or external storage you want to use (in my case it was my 128GB microSD card) and select Apply. A windows will display asking you to confirm the move and ask whether you want to move existing content (which is what you should do). Again, I specified the root drive, but you can easily create a folder and specify it as instead.
Once the default Download folder was moved off the C:\ drive, the next step was to download the 14372 ISO and then mount it. After I ran setup.exe, a message displayed stating more space was needed. Use Disk Cleanup is the default choice, but I selected “Choose another drive or attach an external drive…”
I already had a microSD card with 70+GB free so I used the drop down to select that drive.
Once the D:\ drive was selected, I selected Refresh and the installation continued.
Windows Insider Build 14372 proceeded to install without any issues. Once I had the desktop up, I checked a few things and then opened Disk Cleanup (easily discoverable using Search/Cortana) and used the Advanced button which after a few minutes displayed everything I could delete on the main C:\ drive. I proceeded by selecting “Previous Windows Installations” and acknowledged all prompts.
The Disk Cleanup process gave me a whopping 6GB free.
Next, I opened Settings, Updates and Security, and since this tablet was configured for the Fast Ring, lo and behold, 14385 was offered. And it downloaded and installed beautifully.
Update: I just installed 14393 following basically the same process (run disk cleanup and remove previous Windows installations, insure that the Downloads location is moved to a drive other than C:\ and then install from Windows Update).
This system worked for me and I hope this is helpful. You can reach me on Twitter @barbbowman or in the Microsoft Windows/Windows Insider Forums.
So I wasn’t invited to the Logitech Harmony Ultimate Alexa beta and I have some concerns about how Sonos activities are going to be handled with respect to Alexa’s voice recognition.
It isn’t exactly transparent how to add/configure the Harmony->Sonos->Smart Things->Alexa routines to start Playlists or Stations from your Sonos favorites after you’ve done an initial setup. You have to roll up your sleeves and get a little dirty.
When you edit your Sonos favorites in any official Sonos App (add/remove, etc.) the Harmony App/Remote doesn’t necessarily reread the Sonos lists. To get a revised Sonos Favorites list to refresh for Harmony, you need to START a Sonos favorite, hit the star key on the bottom of the app, then scroll and hit REFRESH. Then you can edit that activity and select a new channel or add Activities and specify a Sonos favorite from the refreshed, up to date list.
Below is a screen shot of the first “page” of (scrollable) activities. The naming convention is something I’m working on, and I’ll explain a little further along in this post. Ideally, I should be able to use the same Activity Name across the board, but this turns out to be problematic and confusing.
When you’ve configured and tested your new or edited Activities, next step is to add a Thing to SmartThings. This, too, isn’t intuitive. Select the + on the Things screen on your phone, then Entertainment, Buttons/remotes. Select Logitech. Your already configured Harmony Hub will appear. Select it, watch the spinning cursor as it refreshes and pulls down your revised, increased list of Harmony Activities. Then select additional activities, watch the cursor spin and the app will populate with the revised list of activities.
Smart Things insists on adding [Harmony Remote] to the end of activities imported from Harmony; you’ll need to edit them to at least remove the [Harmony Remote]. To edit, tap the activity to open its page and then the gear wheel to edit the name. Here’s where the name game becomes interesting. I’ll come back to this when I’m done explaining the process to get all of this hooked up to Alexa for voice control.
The final step is to access the Smart Home tab in the Alexa Echo app. If you have the SmartThings skill enabled, you will need to disable it and then enable it so that it can re-read the list of “Things”. Then you’ll need to re-run Discovery (a pop-up should automatically appear to action this). All of your new activities should now show in the Your Devices list. And you’ll need to do this each and every time you edit or add a “Thing”.
There’s a big gotcha to be aware of. You can’t use the Station name/Playlist Name in your Sonos Favorites. You can’t use any Artist name or recognizable Playlist Name because Alexa will ignore the SmartThings skill and play music natively on Echo/Dot.
Here’s how I learned what works and what doesn’t.
I discovered that when I selected an Amazon Playlist named ABBA (or even the Pandora ABBA Station) from Favorites for the channel to play from Sonos on the Harmony Activity named Sonos Music and linked it with SmartThings and enabled Alexa that every single time Alexa played something else named Sonos on the current Sonos speaker (or already grouped speakers). And completely ignored the SmartThings list. When I renamed the “Thing” to My Sonos in SmartThings and removed/re-added the skill in the Alexa App, I had better luck, but only some of the time.
I similarly had problems with a John Denver and a Judy Collins playlist in Favorites. Alexa consistently ignored the SmartThings skill and played music by (whomever) on the Echo or DOT. .
After the above limitations sunk in, I decided to try a task based name, Exercise Workout. I set that up and was able to use ANY Sonos favorite without confusing Alexa. So in SmartThings, I currently have Sonos Colorado for John Denver and Sonos Folk for Judy Collins (these work). I’ll have to come up with better, memorable names that are task based.
So now I’m going to finish the task of renaming activities on the Harmony and in SmartThings to get this Harmony-Sonos-SmartThings-Alexa setup to work 100% of the time. Probably using task based and/or some other convention that Alexa won’t recognize. If you have any ideas, let me know on Twitter @barbbowman.
And I hope that the same situation isn’t true with the coming “native” Alexa support for the Logi Harmony Ultimate.