Windows 10 Mobile updates for Lumia 930

Recommended Posts


Hi folks,


I'm going to ask a stupid question here, but what is the status of Windows 10 Mobile build, on any ring, for the Lumia 930?


I was under the impression if I was on the Fast Ring, I would still get updates, but I don't know if that's the case. I'm currently running 10.0.15063.540 and as of today (September 18) my device is up to date. I thought I would have seen this one - 15252 - but I've not had anything for a few weeks. And I am aware of the 930 being essentially an old device that is on the cusp of being unsupported/unsupportable (at least as far as MS is concerned).


Apologies for the daft question. I've Googled this, but what I have been reading just doesn't seem to stack up for my device.






Edited by yeoo_andy_ni
  • Like 1
Link to post
Share on other sites

Have you tried switching off of the fast ring (back to Release Preview, for instance), waiting a few days and then switching back to the Fast ring?

Link to post
Share on other sites

Okay, so this is where I'm maybe a little ignorant, but I didn't have the Release Review option from the drop down, just Fast and Slow Ring.

What I did last night was to turn off/leave the Insider Preview and restart my phone. Once I did that, I was able to get a slightly newer build - up to 10.0.15063.608.

So what I am unsure about is if I join the Insider Preview again, will I get any further updates, or is this is for my handset. Or am I now just part of the Release Preview branch. So bloody confusing!

Link to post
Share on other sites

I ended up using the Interop tools to perform the registry hack to make it appear as a Lumia 950, and I instantly got the update.


From what I've been reading it seems that the Lumia 930 is going to live out its days on the Anniversary Update for production and the Creators Update when on the Release Preview ring, and it won't get any updates after that unless you're willing to do some hacking.

Link to post
Share on other sites

Yeah, I've been looking to the Interop tools as the next step to be able to get the updates. I think this is going to be a job when I get home this evening to be honest.


I know this is a little bit harsh, and there is a different set of circumstances for phone/mobile devices compared with PCs, but if Windows 10 can install on a 10 year old Pentium 4 650, with 2GB of RAM, a xxxGB IDE drive and a Geforce 4, why can't my 3.5 year old Lumia 930 support Windows 10 after a certain update. Madness :)

Link to post
Share on other sites

I know your question is meant to be rhetorical, but if you were after some insight into why your case holds true, it's down to how much work Microsoft puts into developing processor-level code for all the different processor types that Windows 10 supports.

The problem stems from the fact that each new mobile-class processor needs its instruction set built and tested independently of each other. Because of this, each new version of Windows 10 Mobile needs to be tested thoroughly on each processor version (Snapdragon 212, 800, 820, etc.) to makes sure that it is 100% compatible. This is also the reason that Android phones become old so quickly; manufacturers aren't prepared to put the time into compatibility testing when they can fully test the latest processor and deprecate the older tech.


So, to your point about how Windows can run well on an older laptop than it can on an older mobile device, it comes down to the work needed to ensure 100% compatibility on the processor level. The Snapdragon 800 processors that power our phones are old enough that Microsoft (rightfully or wrongfully) feels that it's OK to say that our devices have become end-of-life so that they can focus more of their efforts on 100% compatibility testing for the newer processors.


An interesting side-note: This is also the reason that there are only a handful of processors that are considered compatible with Windows 10 Mobile, and why there are no other processor manufacturers supported other than Qualcomm's Snapdragon processors.


Hope that adds some colour to your view of Windows 10. :)

  • Like 1
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Abhay V
      Xbox Live issue preventing Xbox One and Windows 10 users from launching their games [Update]
      by Abhay Venkatesh

      If you were looking to play some games today, heading into the weekend, and fired up a game on your Xbox One or Windows 10 PC only to find that you are unable to access it, you’re not alone. Xbox Support just acknowledged on Twitter that it is aware of an issue with users being unable to access games due to some issues with Xbox Live. The company is actively investigating the issue.

      Depending on some users’ reports on Twitter, it looks like trying to launch games returns a "The person who bought this needs to sign in" message, which likely is due to some authentication issues with Xbox Live. The status page for the service notes that there are issues with ‘Purchase and Content Usage’ that affects launching games or apps. The problem is affecting Xbox One and Windows 10 devices. There is no word on a possible ETA for the restoration of the service.

      Those interested can keep an eye on Twitter or the Xbox Live Status page for updates for more information. Additionally, you can also choose to request for a notification by signing in on the status page and having the site send an Xbox Live notification or text message.

      Update 1: The support account has posted an update on Twitter noting that users should now be able to access their games. However, the status page still notes problems with buying "downloadable" items and launching games.

      Update 2: The Xbox Live Status page has also been updated to reflect that all the issues have been fixed.

    • By Rich Woods
      Microsoft releases Windows 10 build 20241.1005 without any changes
      by Rich Woods

      Two days after Microsoft released Windows 10 Insider Preview build 20241 to the Dev channel, it's releasing a cumulative update. The new build number is 20241.1005, and according to Microsoft, it's sole reason for existence is to test the servicing pipelines. According to the blog post, there are no fixes.

      This is the third cumulative update in the Dev channel in less than two weeks, and all of them have been simply to test the servicing pipeline. This is a normal practice, of course, because Microsoft does have to be able to service its updates. It doesn't seem like something that would be quite as necessary in the Dev channel, being that the Dev channel is strictly for the rs_prerelease branch.

      Of course, this could also mean that the firm is prepping a version for the Beta channel. While the Dev channel isn't tied to a specific release, the Beta channel is. Being that the Windows 10 October 2020 Update, or version 20H2, was released earlier this week, something new should be coming to the Beta channel soon.

      It's unclear what's coming though, because there have been rumors that 21H1 has been canceled in favor of the Windows 10X RTM, something that was originally supposed to happen alongside 20H2 before there were delays. It's also possible that there might still be a 21H1 update, although it could be more similar to the enablement package strategy that we've seen from 20H2 and 19H2. we should find out soon.

    • By indospot
      Windows 10 Team 2020 Update will be available for Surface Hub 2S next week
      by João Carrasqueira

      Earlier this week, Microsoft officially made the Windows 10 October 2020 Update available for the general public, both via Windows Update and through the other usual methods. Following up on that, the company has now announced a release date for the Windows 10 Team 2020 Update, which is starting to roll out on October 27.

      Windows 10 Team is the version of Windows 10 that runs on the Surface Hub family of devices, and it doesn't get major updates all that often. Existing devices are still stuck on version 1703, which is well over three years old at this point. Microsoft released a preview build for the 2020 Update, based on Windows 10 version 20H2, back in July.

      In terms of new features in this update, there's the new Chromium-based Edge browser, support for side-by-side inking with two pens at the same time, and a new Teams feature called Coordinated Meetings, which lets users switch between the Surface Hub and a Teams Rooms device on the fly.

      There are also some improvements for Azure AD-joined devices, such as support for Single Sign-On and Conditional Access. It also enables users to sign in with Microsoft Authenticator or a FIDO2 security key.

      Only the Surface Hub 2S is getting the update on October 27, and even then, it's a gradual release. On that day, users in New Zealand, Australia, Canada, Belgium, and Mexico will start to get the update. On November 10, it will be available in the UK, Japan, Switzerland, and Italy. The United States and Germany will get it on November 30, and the rest of the world starting on December 7. Microsoft says the first-generation Surface Hub, both the 55- and 84-inch models, should get the update soon after.

    • By Abhay V
      Windows 10 build 19042.608 out to the Release Preview Channel with Meet Now in the taskbar
      by Abhay Venkatesh

      After releasing Windows 10 version 20H2 to all users this week, Microsoft is now releasing a new cumulative update for the latest version of the OS in the Release Preview channel. Build 19042.608 is now making its way to Insiders, bringing a bunch of fixes and improvements, and one new feature. The firm is adding the ‘Meet now’ feature in the taskbar that it brought to Windows 10 versions 1903 and 1909 just earlier this week, just as it promised.

      The firm also notes in the blog post that the same 20H2 build will also be released to users in the Beta Channel later today, considering that that channel is also still flighting 20H2 builds. It should not be long before the Meet now feature makes it to the production build and the May 2020 Update, since versions 2004 and 20H2 are technically the same and receive identical cumulative updates.

      Here is the changelog containing the long list of fixes:

      As usual, the update should be made available to users in the Release Preview channel via Windows Update. As mentioned, Beta Channel users will also receive the same update bumping up the build to 19042.608, so those on that channel can check for updates later today.

    • By Abhay V
      Microsoft posts a workaround for the 'Reset this PC' bug plaguing some Windows 10 PCs
      by Abhay Venkatesh

      Microsoft offers an in-built solution to reset a Windows 10 PC through the Settings app if users choose to do so due to a corrupt build or issues with the operating system. The tool also gives users the choice to keep their files and only reset the OS settings to factory default. However, the feature might not be working as expected for some users running Windows 10 version 2004.

      The company today posted a support article acknowledging the issue with the ‘Reset this PC’ feature that causes the tool to fail and prompt an error that reads “There was a problem when resetting your PC. No changes were made". The company also posted a workaround for users who are unable to use the feature and are experiencing the said error.

      Here is the workaround as shared by Microsoft:

      The workaround involves using the Deployment Image Servicing and Management (DISM) tool to attempt to fix the issue. However, Microsoft does not mention any timelines on when a permanent fix for the problem is expected.

      Interestingly, this is not the first time that the problem with the ‘Reset this PC’ feature has been acknowledged. A security update back in February introduced a similar issue and affected Windows 10 versions all the way back to version 1809. The update was then pulled by the company. While today’s documentation only mentions the May 2020 Update, it is not clear if the problem has been fixed for the earlier versions.

      Source: Microsoft Support via BleepingComputer