Nokia Kills HERE Maps for Windows Phone

Now, you truly can’t get there from HERE…

here_maps

In a move that likely has many wondering how long Satya Nadella will allow Windows 10 Mobile to continue to exist, it seems that one of the main staples of the platform, HERE Maps will no longer be developed for Windows 10 Mobile or for Windows Phone, for that matter.

When Microsoft failed to purchase Nokia’s HERE software assets along with Nokia’s hardware business, Nokia decided to sell the asset(s) to an automotive consortium. When that happened, the software disappeared from the Windows Store. The app returned a while after, but apparently, the software is set to make a permanent exist from the platform entire.

Recently, HERE announced that it will be removing ALL of its apps from the Windows Store, including HERE Maps before the end of March 2016.

“In the last few months, we made the HERE apps compatible with Windows 10 by using a workaround that will no longer be effective after June 30, 2016. To continue offering the HERE apps for Windows 10 would require us to redevelop the apps from the ground up, a scenario that led to the business decision to remove our apps from the Windows 10 store.

This means the HERE apps will no longer work on devices running Windows 10 mobile after June 30, 2016. To prepare for this change, we have also decided to remove the HERE apps from the Windows 10 store on March 29, 2016.”

While HERE Maps will continue to work on Windows Phone 8 devices without any kind of disruption, post 2016-03-29, HERE has said that it won’t update the software OR the Maps on that platform at all, except for “critical bug fixes.”

According to HERE, the software is deeply integrated into the Windows Phone OS; and during the development of Windows 10 Mobile, platform changes were made. They felt that the required effort to make the software work on Windows 10 Mobile wasn’t worth the development and testing costs.

While I have a Windows Phone 8 device – a BLU Win HD LTE – that is supposed to be upgradable to Windows 10, this is a bit problematic. One of the biggest draws for Windows Phone/ Windows 10 Mobile is HERE Drive (part of HERE Maps). Without this flagship application, reasons for using devices on the Windows 10 Mobile or Windows Phone 8 platform have substantially decreased. Honestly, with the lack of apps out there for Windows Mobile/ Windows Phone, now that Maps is gone, there really isn’t much use for the platform at all.

Period.

What do you think of this development? Is this the [final] nail in the Windows Phone coffin? Does the platform have any kind of future at all? Why don’t you sound off in the comments section below and let me know what you think?

Related Posts:

Windows 10 – Where Are We?

It’s been six(6) months since its initial release.  How is Windows 10 shaping up?

windows-10 were are we

Introduction

My good buddy Ed Bott recently published an article on the state of Windows 10 from an industry perspective and it got me thinking of my OWN experience with Window s10, now that it’s been out for six or so months.

It’s not all sunshine and daisies.  In fact, there’s a lot that needs to be fixed and changed.  Here’s where I think the new OS stands at this point.

The UI

To say that the Windows 10 user interface is an improvement over Windows 8.x is a bit of an understatement.  The UI is a huge improvement and one that nearly everyone who used Windows 8.x is glad to see.  The Start Menu is back, and it’s something that nearly everyone is happy about.  This single most, familiar UI tidbit is something that’s been around in computing since the release of Windows 95 – nearly 21years – and it’s something that nearly every consumer and corporate user has used and identified with as the beginning of their computing experience that they just can’t seem to give it up. Honestly, seeing as everyone nearly lost their minds when Microsoft replaced with the Start Screen, it’s amazing that people were able to use Windows 8.x at all.  I mean, without a place to Start, how do you get work done?

The other, most noticeable change to the UI is the removal and death of Charms and the inclusion of the Action Center.  The Charms were the UI element that you saw when you swiped in from the right edge of the screen with either your finger or with your mouse cursor.  Those have been replaced by the Action Center, which is a general catch all for notifications and other items requiring… well, requiring user action.

The Action Center has been well received, in my opinion. It’s an easy tool to use, and gives you access to the system events you need to act on.  Charms never did anything of value in my opinion, and were very confusing.

The thing that helped Windows 10 out the most is that, in all reality, its UI is more Windows 7 like.  All of the ModernUI elements are gone.  The ModernUI apps have been changed to Universal Apps and have a totally different look and feel to them.  Isn’t it funny what a new coat of paint will do..?

The Update Mechanism

Microsoft seems hell bent on putting older versions of Windows out to pasture.  It’s a problem they created for themselves with the support lifecycle of Windows XP and the absolute failure and public rejection of Windows Vista. An operating system version should never be in active support for 15 years.

As such, Windows 10 is on an auto update trajectory with destiny.

(Provided you have a legitimate, REAL copy…) If you run Windows 7, Microsoft is going to upgrade you to Windows 10 whether you want it or not… whether you like it or not.  …) If you run Windows 8.x, Microsoft is going to upgrade you to Windows 10 whether you want it or not… whether you like it or not.  There is no opt out.  If you run an earlier version of Windows on your PC, other than a version of Windows 10, you’re going to eventually run Windows 10 on that PC.

Period.

Get over it. Stop complaining and just accept it.  Apparently, there’s not much anyone can do.  Microsoft is hell bent on getting all the world’s Windows users off of their older version of Windows and on to Windows 10… and apparently, they don’t  care who they upset or anger in the process; and it doesn’t matter if you have that version of Windows running on hardware that the OEM won’t support with Windows 10.

In and of itself, upgrading and updating hardware that is on and supports Windows 10, is very easy. All the updates are pulled down in the background.  You don’t even have to run Windows Update. It’s now a service that is run for you and all you have to do – at most – is simply restart your computer.

This is the cool part of the update mechanism.  In fact, you don’t even have to restart your PC. Windows will do it for you and then apply all of the outstanding updates it has downloaded.

It’s the most hassle free way to update Windows… provided you actually want or are really able to run Windows 10.

Recovery

I have yet to have Windows 8.x’s or Windows 10’s Recovery mode/ partition – whatever you want to call it – work correctly for me.  And trust me…. this is definitely NOT a PEBKAC issue (Problem Exists Between Keyboard And Chair).  I know my way around Windows; and honestly…

The feature just doesn’t work.

Most often, the feature doesn’t boot into Recovery Mode. It simply reboots the device, which totally defeats the purpose of the recovery partition in the first place.

When the recovery partition does do something else other than just simply reboot the device back into Windows 10, things usually go very, very wrong.  Wrong to the tune of, “I need to download the recovery image from the internet, create a USB boot stick and try to run that to blow the device and start from factory fresh because my device is now hosed,” wrong.

And to be quite honest, I’ve had the same problem with the recovery partition in Windows 8.x AND in Windows 10.  If you’ve been successful with a restore or complete wipe with the recovery partition running off the device’s internal drive and not off a USB stick, I’d love to talk to you about the experience and the process.

Microsoft’s Signature Hardware

I don’t want to over play this too much. I wanted to start off this section by saying something like, “wow! What a train wreck the Surface Pro and Surface Book are,” but that really isn’t very fair.

Make no mistake.  Both of these devices have some very serious problems.  Both of them have graphics driver issues that (at the very least) are at the root of the disappearing ink issue I’ve been barking about for the past year or more.  The problem is so severe, that it’s also effecting the Surface Pro 3 (a problem, that I think many – including Microsoft – are overlooking).

The Surface Book as graphic driver issues but also has sleep and battery related problems. These problems are so severe that in many cases when users try to put the Surface Book to sleep, the device won’t sleep.  When users try to sleep their computer and then put the device in a backpack or laptop bag, they often get what has been dubbed, “hot bag syndrome.” This is when  the computer fails to sleep, continues to run, tries to “cool” itself with ever warming air (due to it being confined to the small, secure space of a laptop section in either a backpack or laptop bag), becomes overheated and the battery then quickly drops its charge to zero (0).

Having both the disappearing ink/ graphics driver issue along with these battery and sleep issues has made the Surface Book nearly unusable for many.  Thankfully, I haven’t  succumbed to any pressure related to making a Surface Book purchase. The device is simply too pricey to begin with.  To have these simple usability issues on top of it all is nearly unforgivable in my opinion.

While this doesn’t make Windows 10 unusable, it kinda does make you wonder why Microsoft is having issues that it can’t seem to fix with its own, native hardware running its flagship OS, and many OEM’s are not.

I think I’ll just leave that one there to fester for a while…

Conclusion

I’m going to make this short.  Windows 10 isn’t bad, but Microsoft has a ways to go yet, in my mind.

The UI is pretty good, and a much better improvement over Windows 10.  I think Microsoft peaked in 2009 with Windows 7; but that’s my opinion. They haven’t always gotten things right, straight out of the gate.  Heck, it took them three versions of Windows before they got THAT right (Windows 3.0 was the first big hit for Windows, and then it took three versions of Windows 3.x – Windows 3.0, 3.1 and Windows 3.11 – before they got THAT right.

Their update mechanism isn’t bad, but they need to stop forcing the upgrade on users who don’t want it or can’t run it because their hardware isn’t rated for it.  If I don’t want Windows 10, please stop forcing it on me and my under rated hardware.

Their recovery mechanism needs a bit of work. I haven’t been able to make it work right.  Unfortunately, with the way Windows problems work, in many ways its always been easier to rebuild a system rather than troubleshooting it. That isn’t always the case now.

Finally, Microsoft needs to stop screwing around and needs to fix the driver problems in their Signature hardware.  If Microsoft can’t get this right, it’s hard to think that OEM’s and other PC manufacturers will.

Have you had issues with Windows 10?  Are you satisfied with the way it runs on your upgraded or native PC?  I’d love to hear how things are working for you.  Why don’t you join me in the Discussion area below, and give me your thoughts on the matter.

Related Posts:

Windows 10 and Dell Latitude 10 ST2

Well, I found out that Dell doesn’t support Windows 10 on this device…

And isn’t THAT just dandy..?!?

Funny thing is, I’m getting pestered all over the place from Microsoft (via their Windows 10 Upgrade stub) to upgrade the device to Windows 10.

capture

In fact, it (and Microsoft) won’t leave me alone about it.

So, what is a Windows user to do?  Because this is the huge debate and dilemma of Late 2015: My PC OEM isn’t supporting Windows 10 on my device, but since it runs a version of Windows that qualifies for the free Windows 10 upgrade, and the Windows 10 upgrade stub knows this, I get nagged.

I get nagged a lot.  A LOT, a lot; and this creates a bit of a problem.

Microsoft has changed its Windows 10 upgrade options. You used to be able to ignore or defer the upgrade.  Now, you get to upgrade NOW or, later tonight.

windows10-upgrade

Microsoft’s Windows 10 upgrade is a 3.0 to 5.0 GB (give or take a couple hundred megabytes) file that Microsoft is pushing to your computer, whether you want it or not. This upgrade now or upgrade later today stuff has been viewed as malware or spamming mentality.  I’m pretty certain you can still “ignore” the process by clicking the red “X” in the upper right corner (effectively quitting the program), but it’s clear, Microsoft is taking a very aggressive – not assertive, but aggressive – stance on getting people to move to Windows 10, especially on the consumer side.  If you have Windows 7 or Windows 8.x on your personal, home computer, Microsoft has set its sites on you.

This would be fine, if Windows 10 weren’t a train wreck.

It would also be fine if my only remaining Windows machine weren’t unsupported on Windows 10.

Now, to be honest, I’ve got Windows 10 on it already; but there are a huge number of problems with it.  Internet access is difficult on in, as Windows doesn’t always recognize that it actually HAS an active internet connection (though, I’m connected to either Wi-Fi or wired LAN via a USB dongle). Sometimes I have to reboot the tablet four to five times before Windows sees the internet connection. I have no idea why; but this causes a number of different issues, especially with Windows Update (as well as general internet web browsing).

But that aside, it really begs the whole question, of what do you do when the OEM says Windows <the latest version> isn’t supported on your computer?  How do you convince the Windows 10 upgrade app to leave you alone and stop nagging to have Windows 10 installed?

And if it does install (and the experience sucks as bad as it does…), how many times do I have to pull it off before Microsoft and Windows 10 finally leaves you alone and lets you stick with your Windows 7/ 8.x experience?  Unfortunately, Microsoft hasn’t addressed this problem.  They’re assuming – or seem to be assuming – that if the device ran fine under Windows 7 or Windows 8.x that it will run Windows 10 without issue.  I think I’ve shown, or at least convinced myself, that that isn’t always the case.

Barring the forced upgrade issue

(and assuming you get stuck in a periodic, forced upgrade loop) when do you stop downgrading? I’ve actually pulled Windows 10 off my Dell Latitude 10 ST2, twice – once during the Beta period and once after the July 2015 initial release of Windows 10.  As far as I know, as long as you have a pre Windows 10 version of Windows on your PC, you’re going to get hit with this time and again (especially since the downgrade process doesn’t always work and in many cases people have to blow their PC’s and start over, or use a restore DVD/ USB stick to get back to an earlier version of Windows).

Microsoft is giving everyone who upgrades 30 days to go back to their previous version.  Have you decided that Windows 10 wasn’t for you?  I haven’t heard of too many individuals that have fallen into this trap or have been forced to upgrade only to put their computer back to the previous version, though I’m certain that some have done that.  Unfortunately, Microsoft isn’t making stats on those that have reverted to their previous Windows version available.  When they have a 1B user target their trying to hit, I’m certain that they aren’t wanting to advertise how many people have downgraded their PC.

Have you bumped into this problem?  Is your computer officially unsupported on Windows 10 (as mine is)? Have you been forced to upgrade your computer? If so, what’s the experience like?  Did you downgrade back to your previous version of Windows?  Did Windows pester you and make you upgrade again?  How did you make it all stop?  I’d love to hear from you if you did.

Related Posts:

Why I Ultimately Dumped my Surface Pro 3

There comes a time when enough, is just enough…

Surface pro 3

Its hard to know where to start with this one.  I’ve been a Windows guy for so long – nearly 20 years – that in the end… I feel like I abandoned my post, or something.  However, there comes a time when you know you’ve fought the good fight and that you just can’t fight any more. I never thought I would ever say this, but personally, I really think I’m done with Windows and Windows 10. So much so, that I’ve sold my Surface Pro 3.

Over the past year, I’ve written a bit on how much of a problem OneNote and Windows 10 can be together. Funny thing is, I thought it was limited to Office 2013.  Unfortunately, its not.

Even with OneNote 2016 ink still disappears on all Surface Pro tablets running both Windows 10 and OneNote.

I’ve also noticed that while things should be getting more and more stable on Windows 10, they aren’t.  They just aren’t.  Not on my Surface Pro 3.

And to be quite honest, I was willing to live with it. I was going to figure out some way to work through it. I wasn’t going to be easy, but I was resigned to it, in a sense.

That is until I found this thread.

This is not going to end during the life cycle of this device. Period.

The problem exists on the Surface Pro 4. Though it’s a bit different, it’s the same type of problem.

It became clear to me after reading through that thread, that its not going to end. So… I sold my Surface Pro 3. What have I replaced it with?

Nothing yet.

Honestly, I’m not certain what I should do at this point.

The Surface Pro line is proving to be a bit unstable and honestly, unreliable for what I need it to do.  Its also a bit more expensive than I want or need it to be.  I am looking for a way to take hand written, notes in meetings.  The Surface Pro 3 was perfect for that, to a point. It ran OneNote 2013 well enough.

So why not return my Surface Pro 3 to Windows 8.1?  That’s a fair question…

There are really two big issues here:

  1. Windows 8.1 is Clumsy
    Windows 8.1 still has the Windows 8 UI. While there are apps like Start8 and ModernMix that can help hide some of the issues and problems; but its really just a coat of paint for both the Start Screen and ModernUI based apps, nothing more.
  2. Windows 10 isn’t Going Away
    Microsoft is getting aggressive with Windows 10. Their Windows 10 upgrade stub that installs as part of a Windows Update component.  While you can defer it for a while, its going to do its best to assert itself on your computer. I’m not entirely certain you can say no forever. I may be wrong – I hope I am – but it may be true.The OS has been downloading to computers without the consent of their owners. It could install itself overnight, also without their consent.

I thought long and hard about just taking my Surface Pro 3 back to Windows 8.1 and just using Office 2013 or Office 2016 (and ultimately OneNote) there. However, in the end, I decided against that, largely because of number 2, above.

So, out the door it went.  I just wasn’t willing to deal with its problems and issues any longer. I had had enough.

At the end, when I went to take my Surface Pro 3 back to Factory fresh with Windows 10, I had all sorts of trouble, too. Windows 10 would not reset itself on my Surface Pro 3.  Most of the time, it prepped itself and then simply restarted and went back to my Windows 10 account. When I tried to use the Advanced Restart Settings – which booted to the UEFI where you can also refresh, reset and even wipe the drive if you wanted – my Surface Pro 3 froze when trying to reset itself… more than once (I know because it sat at that screen for over three hours each time I tried. I tried three times…).

I had to pull the Windows 8.1 recovery USB I made many months ago and use it; and even then, it wasn’t smooth sailing with that either. I had trouble resetting the device with that too. I had to try ore than once with it, and then ultimately I had to wipe the drive to get MY data off when it sold.

What does this mean for you?

Probably not too much, unless you’re having similar ink and stability issues with Windows 10 on your Surface Pro device (the thread that I’ve been referencing with disappearing ink has a couple posts in it which indicate that it also happens with the original Surface Pro and the Surface Pro 2 as well).

If you are, then you have some kind of decision to make – either put up with it, stay on or move back to Windows 8.1, or sell yours, like I did.

Do you have a Surface Pro device?  Are you having issues with disappearing ink?  Is yours unstable?  Are you using Windows 8.1 or Windows 10? Are you using Office 2013 or Office 2016? Why don’t you meet me in the discussion area below and give me your thoughts on this and tell me what you think you’re going to do?

Related Posts:

Microsoft Releases Windows 10 Build 10576 to Fast Ring Insiders

The latest build of Windows 10 has been issued. Here’s what it’s got…

Windows10mic

If you’ve been following me over the past year, you know that I’ve been a Microsoft Windows 10 Insider since the first released build of Windows 10 to Insiders back in October of 2014. Over the past year or so, there’s been a boat load of new builds released to the Fast Ring. Some have been good.  Others… not so good.

While the jury is still out on the quality of Windows 10 Build 10576, it is the next item up for bids…

New Features

  • Media Casting in Microsoft Edge: You can now use Microsoft Edge to cast video, picture, and audio content from your browser to any Miracast and DLNA enabled device on your network. Please note: Casting protected content (content from places like Netflix and Hulu) is not supported.
  • Ask Cortana inside PDFs in Microsoft Edge: You can now highlight text while reading a PDF in Microsoft Edge and right-click to “Ask Cortana” to find additional information.
  • Updated Xbox beta app for Windows 10: The Xbox beta app for Windows 10 was updated last Friday which includes the ability to easily find and add Facebook friends who are also on Xbox Live to play, chat, and share clips – a top requested feature. In addition to that new feature, voiceover recording functionality has been added to Game DVR, and the Store in the Xbox beta app will allow you to search for and purchase Xbox One games – including Games with Gold and Deals with Gold promotions, and Xbox One 25-digit codes will be redeemable within the app.

Fixes

  • We fixed the issue where the Xbox app for Windows 10 would consume gigabytes of memory on your PC if you have any Win32 games (non -Windows Store games) installed on your PC that have been identified as games or added by you in the Xbox app.
  • We introduced an early preview of nested virtualization so that people could run Hyper-V Containers in Hyper-V virtual machines with Build 10565. This build includes performance improvements.
  • We’ve been addressing a lot of feedback around localization text UI in various languages and you’ll see a lot of that work in this build.
  • The search box should now work in this build if you are in a locale where Cortana is not available.

Known Issues:

  • To continue receiving missed call notifications and send texts from Cortana, you will need to be on this build and higher. We’ve made a change that improves this experience that requires newer builds.
  • When notifications pop up from Action Center, any audio playing (like music from Groove, or videos from the Movies & TV app) gets reduced by 75% for a period of time.
  • After upgrading to this build, all your Skype messages and contacts are gone in the Messaging app. The workaround for this is to navigate to this folder in File Explorer:
  • C:\Users\<USERNAME>\AppData\Local\Packages\
  • Microsoft.Messaging_8wekyb3d8bbwe\LocalCache
  • Delete or rename the “PrivateTransportId” file.
  • Then restart the Messaging app.
  • Small form-factor devices, like the Dell Venue 8 Pro, that boot with rotation or virtual mode screen size set larger than the physical screen size will experience a bluescreen on upgrade and will roll back to the previous build.
  • After upgrading to this build, the power button on your Surface Pro 3 may no longer put your Surface Pro 3 to sleep and instead shut down.
  • WebM and VP9 have been temporarily removed from builds. We continue to develop a VP9 implementation that we intend to ship in Windows. Expect VP9 to return soon in a future build.

Conclusion

I give top marks to the Windows 10 Team here. They’re really trying to get this thing ready for release. They’ve also had a number of different quality and stability (as well as privacy) issues to deal with. Not everyone, myself included, is happy with the current state of Windows 10, either in a released or prerelease state.

It still need a great deal of work.

It’s still not ready… though it’s slightly better than it was.

However, it’s clear that there are still a number of issues with Windows 10’s update mechanism – Windows Update – still… especially on a Surface Pro device and especially when it comes to firmware updates.

I know that I’m not the only one that continually sees the download of firmware or hardware updates for their Surface Pro device.  They can get repeated many, many times in both failed and successful installs.

The biggest problem here is that my Surface Pro 3 very rarely actually runs through the firmware update process.  Yes, Windows Update restarts my Surface Pro 3; but it doesn’t always update the firmware, even if it hasn’t been applied (or truly updated) on the device.  And before anyone asks, yes, it has actually reapplied a firmware update more than once, though more often than not, it just redownloads the firmware update, SAYS that it’s going to reinstall it, doesn’t finish the firmware update, but lists the reapplication as successful anyway.

Go figure…

Are you (still) on the Windows 10 Insider Fast Ring?  Have you been installing all the updates?  Have you installed the latest build, Build 10576?  What do you think of the current state of Windows 10?  Why don’t you meet me in the Discussion area below and give me your thoughts on these and other Windows 10 related issues. I’d love to hear them…

Related Posts:

UPDATE – OneNote 2013 and Windows 10 – Potentially Lethal

It’s been a long time coming, but there finally seems to be light at the end of the tunnel…

onenote and windows 10

I’ve been using the Surface Pro 3 at the office since December of 2014.  Prior to that, I used a Surface Pro 1 for a couple of years. It was the best and easiest way to really organize work at the office; and I say this to any and everyone who asks why I use it:

  1. It’s the best digital notepad (with OneNote) I’ve ever been to find and use
  2. With OneNote on the web and/ or OneNote’s sync capabilities, you have access to your notes nearly everywhere you have a device with internet access
  3. Paper notepads, notebooks and portfolios get lost. You’re never going to leave a tablet in a conference or meeting room (they’re too expensive to forget)

It’s a nearly flawless system, and it’s one of the best out there. Other software and hardware tools just don’t have the same capabilities or use cases due to one limitation or another.

When the Surface Pro 3 was released, I knew it was worth the upgrade from my Surface Pro 1, so off it went toGazelle, and over to the Microsoft Store I went.  While Windows 8.1 wasn’t as optimal a notebook experience as I wanted, and while (in my opinion) Windows still doesn’t know if it wants to be a desktop or tablet OS (even with Windows 10); with either Windows 8.1 or Windows 10 (and the right utilities, like Start8  from Stardock Software) it can still be a very productive tool in either an corporate or academic setting.

Until, however, you move to Windows 10 and you bump into the problems I mentioned in March of 2015.  The Disappearing Ink Bug is a huge problem for users of the Surface Pro 3.

It completely negates nearly all the value out of the device.

The reliability of the inking system is nearly gone. You never know when you’re going to lose anything you’ve written down, as the bug is completely random, and in end, you’re left with two very real choices – downgrade from Windows 10 to Windows 8.1 or take your chances with Windows 10, the bug, and maybe you lose some notes or maybe you don’t.

Well, I have a bit of an update for you.  There appears to be, what may be, a final fix for this problem.  There are two very active threads on this issue over at the Microsoft Support Community (here and here).

Microsoft has released KB3093266 in response to disappearing ink on the Surface Pro 3 running Windows 10.  This cumulative update addresses not only disappearing ink, but tap becomes right click as well.  Both of these issues were contributing factors to the conditions being experienced (where ink would vanish in OneNote on a Surface Pro 3 running Windows 10).

The cumulative update available via Windows Update on your Windows 10 PC, may take a while to appear on your Windows 10 PC. Like all Windows Updates, Microsoft rolls them out in batches.

Unfortunately, I haven’t had it show up for me yet.

However, one really good point came up out of (this support thread. I wish that I could take credit for it, but I really can’t.  Credit for that goes to Clayton Dittman

“Can you possibly tell the Windows OS team to check with the surface team and tell the surface team to check with your team before releasing an Operating System which breaks core functionality of your Staple Devices?

I cannot in good conscious use a Surface (Pro or not) again because of the way this migration to Windows 10 was handled in lieu of Office 2016 and the Surface Pro 4.

I want to trust Windows, I want to depend on you guys for quality control and solutions my customers can trust. I just can’t…”

While it seems obvious, the reliability and trustability of Windows 10 for many users has greatly diminished.  It’s not just this issue, there are still huge privacy, stability and (other) reliability concerns.  You can check just about any and every Windows blog on the internet today and find at least 2-3 articles covering all that.

The cumulative update I mentioned may resolve the disappearing ink issue… it may not.  KB3093266 is not the first fix that was released to address the issue.  There were individual updates made to Windows 10, OneNote 2013/2016 as well as Office 2016 that failed to resolve the problems between May and September of 2015.

Results from those that have received this update have been generally positive, though somewhat mixed.  Generally, it seems to be working; but like Dittman noted above, how much damage has TRULY occurred for the Windows and Surface Pro brands?

How easily Microsoft can recover from this is going to depend on a couple of things:

  1. Does the cumulative update truly resolve the bug for all users of both the Surface Pro 3 and the Surface 3 (its actually experienced on nearly all Surface Pro devices as well as the Surface 3)
  2. How well the Surface Pro 4 is received
  3. How well the bug stays resolved (especially on the Surface Pro 4)

Every time Microsoft releases a cumulative update or a new build, this issue is going to have to be retested. It’s very possible given the depth and severity of the problem(s) that Microsoft may resurrect the issue in future builds and updates. While that’s not ideal and certainly won’t be intentional, it does happen quite often with software development. It’s simply the nature of the beast – sometimes, it comes back.

The Surface Pro 4 has been anticipated for many months now. While there’s no real evidence that any industry pundit can provide regarding a credible rumor on the device’s ACTUAL existence, it is said that Microsoft will announce something next week (2015-10-05 to 2015-10-09) with an actual release date also rumored to be SOMETIME this month (October 2015).  While it totally misses Back to School, it should hit the 2015 Holiday Buying Season, provided its already being manufactured.

Do you have a Surface Pro device (1, 2 or 3)?  Do you have a Surface 3?  Are you using OneNote and the Surface Pen to take notes?  Are you experiencing issues with floating and disappearing ink?  Have you been following any of the Microsoft support threads I mentioned (here or here)?  Have you received the Windows 10 Cumulative Update (KB3093266) that I mentioned?

If you have, do, etc. and have received the update, I would REALLY appreciate hearing back from you on this.  Please provide the appropriate comments and/ or information in the Discussion area, below, so that I can get your information back to Microsoft.  This is a huge bug, and really needs to be resolved once and for all.

Related Posts:

Updating Windows 10 Mobile After it goes RTM

Microsoft says that it wants to push rapid updates to users; but there are issues…

Windows 10 mobile

I saw an interesting update on the Supersite for Windows this morning, and I answered a comment asking what the issues were on this in the US. I wanted to expound a bit more, so I thought I’d gather what I wrote and then start shooting my mouth off.

The original article deals with Microsoft taking control of OS related updates from the mobile carriers – in the States, that’s basically, AT&T, Verizon, T-Mobile and Sprint, but may also include a number of larger regional or budget carriers like US Cellular, Cricket and Boost Mobile – and making updates available roughly four to six (4 – 6) weeks after the updates go RTM. Based on a report from Ed Bott, Microsoft is serious about it. According to Terry Myerson,

“Here at Microsoft, we take our responsibility to keep Windows secure seriously. We follow up on all reported security issues, continuously probe our software with leading edge techniques, and proactively update supported devices with necessary updates to address issues. And today, we’re announcing this continuous update process applies to all Windows 10 devices, including phones.”

The only way that Windows as a Service (WaaS) REALLY works, is if Microsoft can release updates to users as they are ready.

The problem is that mobile broadband carriers in the US don’t allow just anything to ride their networks and don’t allow hardware manufacturers or OEM’s to release just any device update without that update going through a testing and certification process. Well, at least everyone but Apple; users of any cellular capable iDevice get iOS updates all the time…as soon as they’re released, in fact. I’ll deal with Apple in just a bit. However, every other device and device manufacturer/ OEM has to jump through a lot of hoops.

There are two parts to this issue: Control of the (enterprise) network and control of support. The second one is easy to understand. The first one is a PITA.

Control of Support
Many users don’t know much of anything about their smartphone past how to make and take calls, send and receive text messages, and change a status update on Facebook (or other social network). Most carriers like these types of users, because they generally accept what they are given, even if they don’t like it (which leads to the first thing, but I’ll get to that in a minute).

Because most users aren’t very tech savvy, they don’t know how to trouble shoot issues when they bump into problems, so they call their mobile carrier for support. The mobile carrier knows that support is a big issue, and don’t want to HAVE to support each and every problem that can arise, especially with exotic or little/unknown 3rd party software. So, they offer crapware that may have much the same functionality that most users are looking for and do their best to push users that way. They pay their support people to troubleshoot the crapware, and to try to get users to use it instead of a similar, and likely much more popular app that does the same thing. They can’t pay their people to know everything about every chat client, social network, photo enhancer, etc. it costs too much money to train and support them.

Control of the (Enterprise) Network
(Most) Mobile carriers don’t allow just ANY smartphone on their network. Unknown or rogue mobile devices can eat up bandwidth; and as much as they want to charge you for the bandwidth you use, mobile carriers certify devices and updates because if it rides on their network, users are going to demand support, so… they limit what can actually get on the network… or they at least try to.

Historically, this is why mobile carriers take so long to test individual devices before they actually offer them for sale; or take so long to test and certify updates before they actually go out to users of devices that use the mobile network.

Think of this the same way you think of your work computer. Your office’s IT department doesn’t let you install everything from any and every download site on the internet. Many sites are blocked to protect the network from viruses and other malware. It’s the same thing here.

All you do is use the network. You don’t own it, so the mobile carrier doesn’t allow you to do any and everything you want…. just like the office. The purpose is public communication. Your use effects the public, and the carrier has an obligation to insure that its available to all that pay to use it.

Now, all of this is SOMEWHAT based on older information. I really ran into this face first when I was a Verizon customer, living in Nashville, TN back in 2003/ 2004. I had two separate talks with a VzW store manager and a Tier 2 install technician (I had a car kit installed for my then, state of the art new, Samsung i700). The install tech who put the car kit in my Honda CRV laughed at me when I asked him why the store staff wouldn’t talk to me. I have to admit, it was kinda funny. However, he explained that I gave them fits because I knew more than they did, and had issues they couldn’t support (smartphones were new back then…). I later confirmed this with the store manager, who apologized, but didn’t offer any helpful suggestions, either.

However, the general principals here are the same now as they were then. Control… at least until you pay me (me, being the mobile carrier). Apple cut a lot of deals to get the iPhone on AT&T (and eventually VzW and T-Mo). Part of that was specifically that Apple has control of OS updates. It worked, and continues to work because Apple sells a BOAT load of iPhones. Mobile carriers make a lot of money via mobile accounts, upgrades, and other add-on related iDevice purchases.

…and volume. Let’s not forget the amount of sales volume they get. The carriers tolerate it because they make a lot of money based on iDevice sales volume.

Microsoft has a huge issue here. They simply don’t – and won’t – have the device sales volume to help them convince mobile carriers not to relinquish they’re control of their networks so Microsoft can deliver both software and firmware updates as needed. I have no idea what incentive Microsoft thinks it’s going to come up with to convince the carriers to allow this to happen. However, you would have to think that it may involve a bit of that ol’ happy cabbage… We’ll have to wait and see what and how MS does to make this happen.

What do you think about all of this? Will Microsoft be able to release updates to Windows 10 Mobile device owners as they want to; or will the US mobile carriers put a halt to it? Would these OS and firmware updates attract you to a Windows 10 Mobile device over, say, an Android device or iDevice?

I’d really like to hear from you on this, so why don’t you join me in the discussion area, below, and give me your thoughts on it all.

Related Posts:

OneNote 2013 and Windows 10 – Potentially Lethal

The union is proving to be very problematic…

onenote and windows 10

I’m a huge OneNote advocate. In fact, it’s the major reason why I’ve been using a Microsoft Surface Pro series tablet since their initial release in 2012. The ultrabook’s active digitizer, pen and OneNote create a digital notepad experience that can’t be beat in a corporate meeting setting. I wouldn’t want to take notes in a meeting any other way.

When Windows 10 came out, it was natural for me to pursue placing it on my Surface Pro 3. I was a formal part of the Microsoft Technical Beta Team between 1996 and 2002. I’ve been an active Windows beta tester via my company’s IT department since time began, so I’m used to working on systems and with hardware with beta software on it. It’s become second nature to me.

OneNote on my Surface Pro 3 under Windows 8.x worked as intended and expected. It’s all released software with some maturity on it, so I expected everything to go smoothly; and it did.

With Windows 10, its been somewhat of a different story.  With Builds 9879 and older, things were fine.  While the OS may have been a bit buggy, OneNote appeared to be functioning as a mature, released productivity application running on a buggy, beta OS. In other words – situation normal.

With build 9926, however, things have taken a drastic step backwards.

The OS is still buggy and problematic, but that’s to be expected. It’s still a beta of an unreleased OS.  However, OneNote has become increasingly unreliable.  Unfortunately for me, this behavior has bled outside of the OS.  There seems to be something going on with OneNote 2013, specifically in Windows 10, as I’m not seeing this behavior anywhere else I have the software running.  And that… I find very concerning.

Pen and inking services are directly controlled by Windows.  This is where I’m having the issue and problems, and since OneNote 2013 is relying on Windows 10 to create digital ink, interaction between OneNote 2013 and Windows 10 Build 9926, seems to be at the heart of the matter.

OneNote 2013

OneNote 2013 exhibits a disappearing ink problem where drawn, digital ink just vanishes, never to be seen again, regardless of whether or not a notebook has synchronized or not.  It usually starts happening 3-5 minutes after the application has been opened.

Desktop OneNote doesn’t show any symptoms of the problem prior to ink disappearing.  Ink just…vanishes. It’s not ALL ink, or all ink after a specific amount of time has elapsed or a specific even occurs.  Some in may vanish.  Other ink may not vanish. Disappearing ink can be letters, words, sentences or whole passages of digital ink.

There’s no pattern to this. There’s no “tell.” There’s no way for me to state or predict with any level of accuracy what so ever, that after “this” point in the app, after being open for a specific period of time, or after writing a section of digital ink, that any, some or all of the ink will disappear; and it doesn’t disappear immediately after you stop writing.

It might take 15-45 seconds or so and then, when it does disappear, it doesn’t blip, blink or otherwise show you that it’s there, but invisible or merely “forgotten.” It’s truly no longer part of the file.

It may be removed as part of the “save,” as that part of the file was never part of the file to begin with. It may not.  I have no idea… and I think THAT more than anything annoys me the most.  I can’t catch the pattern, and either reproduce the issue on demand, or prevent it from happening.

OneNote Preview

OneNote Preview for Windows 10 also has a disappearing ink problem; but there’s a bit of a difference here.  OneNote Preview has a tell.  The current page you’re working with, freezes.  you can still ink on the page, but the page won’t move up, down left or right.  The app may then stutter, and/or closes and all of the ink that was written to a page from the point of the stutter forward – when the page freezes or refuses to move – disappears.

OneNote Preview also auto-minimizes at times. When its window is restored, the app displays its splash screen and then hangs or appears to hang. You can minimize/ restore the window all you want, but the app may or may not “reactivate” at that point. Your may have to force quit it and restart it. On many occasions, I’ve had to bounce my SP3 to get OneNote Preview for Windows 10 to run correctly again.

OR…

The app may recover and may or may not have had ink disappear.  I’ve noticed this behavior in OneNote Preview, and the app can “recover,” but the ink that was written while the app was in that “bad state” is lost. Ink written after that (i.e. when the screen “unfreezes,” is saved.  OR, the app may have a state so severe, that the Window won’t restore, and you have to quit the app via Task Manager or, if possible, tap and hold the icon on the Task bar and then choose “Close.”

I’ve been dealing with this now on and off for the past 3-4 weeks.  Its put a huge dent in  my productivity at the office, as I can and have lost whole paragraphs of written notes that I thought were “safe,” and ultimately were not.

While writing this, it was announced that Microsoft may be releasing a new Windows 10 build as early as 2015-03-13; and also announced plans to step up the frequency of its Windows 10 builds in its Insider’s “Fast” release ring.  If and how any resolution to this issue is introduced in any new builds of Windows 10 or Office 2013 will of course, be the subject of an update here on Soft32, and I will definitely keep everyone posted.  If you having issues with OneNote and Windows 10, I’d love to get the details from you in the comments section, below.

OneNote Tweet 01 OneNote Tweet 02

Related Posts:

Stay in touch with Soft32

Soft32.com is a software free download website that provides:

121.218 programs and games that were downloaded 237.780.356 times by 402.775 members in our Soft32.com Community!

Get the latest software updates directly to your inbox

Find us on Facebook