Microsoft has stated over and over that users of older Windows version should migrate to the new Windows 10 releases as they won’t continue to get support. The company has announced the dates on Monday, that the new apps submitted to the Microsoft Store with Windows 8.x and Windows Phone 8.x will be shutting down.
The updates to those apps will only made available using Windows 10 devices.
As a part of the Windows device life-cycle, Microsoft Store will “soon stop accepting new apps with Windows Phone 8.x or earlier or Windows 8/8.1 packages (XAP and APPX),” said Microsoft. Soon after that date, “we will stop distributing app updates to Windows Phone 8.x or earlier and Windows 8/8.1 devices; at that time,” the company added.
Important date to take note for effective planning, development cycles:
The first and the foremost date is the “October 31st, 2018,” it’s this date when Microsoft will stop accepting new app submissions on Windows Phone 8.x (or earlier) and Windows 8/8.1. Since this will not affect existing apps, updates for these apps will still accepted.
Next up, beginning on July 1st, 2019, Microsoft will only made available updates through Windows 10. The updates to apps with [Windows Phone 8.x or earlier packages] can still be published, and will only be made available to Windows 10 devices.
And, finally, Windows 8/8.1 devices will no more receive apps, updates beginning July 1, 2013. Updates to all apps, including on Windows 8/8.1 can still published.
Yet, these updates will only available to the Windows 10 devices.
Time and again, the company has been encouraging developers to explore the new Universal Windows Platform (UWP) platform, that allows creating a single Windows 10 app deliverable onto all devices.
Interested, you can learn more about UWP apps here.
In the other Windows news, Microsoft recently on August 16 published a new Windows 10 19H1 test build to the Skip Ahead. Alongside ‘Redstone 5’ Build 17741 to the Fast ring.
- Reliability improvements in Narrator reliability
- Scan Mode improves the reading and navigating along with selecting text. Selecting forward in Edge still has some issues.
- QuickStart can now be launched via a new link in settings should now launch from the very first Welcome page. Narrator, when launched, will now start reading it automatically.
- Move Next, Move Previous, and Change View: When changing Narrator’s view to either character, words, lines or paragraphs the Read Current Item command will read the text of that specific view type more reliably.
- Keyboard command changes: The keystroke to Move to beginning of text has changed to Narrator + B (was Narrator + Control + B), Move to end of text has changed to Narrator + E (was Narrator + Control + E).
- Braille: Improved usage of Braille is commanding when using the Narrator key from the braille display.
- Keystroke to provide feedback has changed to “Narrator + Alt + F,” and works both in the Standard and Legacy layouts. The Legacy layout also allows you to use Narrator + E to send us feedback.
As far as we know “19H1 is a replacement Codename for the build that many had assumed would be called as “Redstone 6.” It’s the feature update to Windows 10 that will follow Redstone 5 and will be released around April 2019.”
Microsoft is reportedly planning to add a new sandbox security feature to the Windows 10 called “InPrivate Desktop.”
“InPrivate Desktop for Windows 10 will serve as a [throw away sandbox for secure, one-time execution of untrusted software].” It looks to work like the Windows Defender Application Guard (WDAG), which helps to fight malware by confining malicious content and exploits downloaded from the web.
Though, Microsoft has yet to confirm this new sandbox security feature, but according to reports “InPrivate Desktop will debut as part of a future release for Windows 10 codenamed [19H1], ZDNet blog speculates.
The feature will need at least 4 GB of RAM, 5 GB of free disk space, 2 CPU cores, and hypervisor capabilities enabled in the BIOS.
Also, a new RS5 Build 17741 got released to the Windows 10 Insider in the Fast ring and introduces a new and easier way to get to the Your Phone app.
A recently added “desktop pin” now take you to the Your Phone app. Also, you can go through all the apps list in Start Menu, or Windows key and search for Your Phone app.
“Link your mobile phone to your PC through Your Phone app. Open Your Phone app and follow the setup flow. You will receive an app from Microsoft which you must download to your mobile phone and follow the setup prompts. Android 7.0 and above are compatible with Your Phone app. For PCs tied to the China region, Your Phone app services will get enabled in the future.”
Your Phone app is also live for Insiders who are in Skip Ahead running 19H1 builds.
On August 14, Microsoft released a new build of the Windows Server vNext Long-Term Servicing Channel (LTSC) release with both Desktop experience and Server Core, as well as a new build of the next Windows Server Semi-Annual Channel release, Microsoft Hyper-V Server and Windows Admin Center 1808.
Windows Server 2019 Insider Preview Build 17733 can downloaded over here.
Windows Admin Center Insider Preview 1808 with new infrastructure to support future scenarios and improvements to the experience for the Azure Site Recovery and Azure Update Management hybrid scenarios was released on August 14.
Server settings such as environment variables, remote desktop, and RBAC settings are now available as a standalone tool at the bottom of the tool list in the Server Manager solution.
Hyper-V host settings are also available on standalone servers and clusters with Hyper-V enabled. The Hyper-V host settings on a cluster allow you to change configurations across all cluster nodes at once!
In Virtual Machines, a new security settings section has added to the individual VM settings.
Additionally, an update to the Windows Admin Center SDK Preview with added CLI, ability to target different SDK versions, refreshed SDK examples for tools, solution and gateway plugin and updated publishing options.
Windows 10 SDK Preview Build 17733 is also available now for download from the developer section on Windows Insider.
Web Authentication in Microsoft Edge introduced on July 30 as an easier way for users to sign in with their face, fingerprint, PIN, or portable FIDO2 devices, leveraging strong public-key credentials instead of passwords.
Windows Hello allows users to authenticate without a password on any Windows 10 device, using biometrics— face and fingerprint recognition— or a PIN number to sign in to websites. With Windows Hello face recognition, users can log in to sites that support Web Authentication in seconds, with a glance.
Users can also use external FIDO2 security keys to authenticate with a removable device and your biometrics or PIN. For websites that are not ready to move to a completely passwordless model, backward compatibility with FIDO U2F devices can provide a strong second factor besides to a password.
Here is a GIF animation showing a purchase using Web Authentication via Windows Hello:
For getting started, check out this Web Authentication dev guide.
Windows 10 IoT Core Services, which enables IoT partners to commercialize their solutions running on Windows 10 IoT Core is now released under the public preview along with details on purchasing and pricing.
IoT Core Services provides 10 years of operating system support along with services to manage device updates and assess device health.
Though, Windows 10 IoT Core operating system remains royalty-free. Windows 10 IoT Core Services, which is a paid offering that can added depending on the following scenario:
- Businesses and solution integrators can buy IoT Core Services through an Azure subscription. The subscription price will be $0.30 per device per month when the product releases later this fall. During the preview period, the price is $0.15 per device per month.
- Partners enrolled in our Cloud Solution Provider (CSP) program will be able to resell the service and establish ongoing relationships with their customers. They can sell a flexible, pay-as-you-go subscription as needed to meet device requirements. This option will be available later in the year.
- OEMs can license the service with a device by pre-paying for the service. This option will be available later in the year.