Announcing Windows 10 Insider Preview Build 14342

Hi everyone,

Today we are releasing Windows 10 Insider Preview Build 14342 to Windows Insiders in the Fast ring. The Language Packs for this build will be live later tomorrow.

Here’s what’s new in Build 14342

Updates for Extensions in Microsoft Edge: Instead of extracting and loading extensions from a local folder, all available extensions can now be downloaded directly from the Windows Store. This change means that your currently installed extensions will be removed, and you’ll have to reinstall the ones you want from the Store. Then in future updates, your extensions will be automatically re-downloaded and installed.

We also have some new extensions available for you to try out. We are excited to announce that starting with this build, both AdBlock and Adblock Plus are now available for download in the Windows Store in addition to Pin It Button, Mouse Gestures, Reddit Enhancement Suite, Microsoft Translator, and OneNote Web Clipper. It is recommended that you only install one of either AdBlock or Adblock Plus as having them both running at the same time can cause issues with viewing websites in Microsoft Edge.

Important note: There is a bug in this build that occurs if you turn off all extensions without uninstalling them, you may not be able to close the browser or get context menus to work. To avoid this issue, uninstall any extensions you no longer want to use instead of turning them off. If you do hit this issue, to get out of this state you will need to turn on one or more extensions or uninstall all extensions, kill any Microsoft Edge processes running in Task Manager, and restart Microsoft Edge.

Real-time web notifications in Microsoft Edge: Microsoft Edge now supports real-time web notifications, which allow participating websites to send notifications to you via Action Center, with your permission. For example, when your friend sends you a message on Skype for Web while you’re busy in the Xbox app, you won’t miss a thing. A notification from the website will appear in Windows, just like an app might send. Click on the notification and you’ll be right back in Microsoft Edge at the site that sent it!

Swipe navigation in Microsoft Edge: Since the release of Windows 10 Mobile, our top feedback request for Microsoft Edge has been asking for the return of the swipe gesture to navigate back and forward. It’s also been one of our top 10 requests on PC. With this build, you can now swipe from anywhere on the page to get back to your previous page. This will be coming in the next Mobile build as well!

Bash on Ubuntu on Windows Improvements:

  • Symlinks within the Windows Subsystem for Linux are now functional on the mounted Windows directories. This fix helps support many scenarios including the npm installer.
  • Users with non-Latin Windows usernames are now able to install Bash on Ubuntu on Windows.
  • Many more improvements can be found in the WSL release notes here!

Skype UWP Preview Update: The Skype UWP Preview app has been updated will be updated tomorrow (5/12) via the Store in response to your feedback. In this release, you have the ability to set a dark theme and can switch between different Skype accounts. You can expect mobile release in the June timeframe.

Updated Windows Ink Workspace icon: We have updated the Windows Ink Workspace icon on the taskbar. The new icon shows a more expressive ink stroke and is more consistent with other icons in the notification area. The new icon also looks better at wider range of sizes. 

Updated visuals for User Account Control dialog: The UAC dialog now supports dark mode! As part of this work, we’ve updated also the header color from yellow to blue.

Dark mode UAC Prompt

Middle-click for dismiss in Action Center: Action Center now supports the popular dismiss model of middle-clicking on a notification via the middle button scroll wheel on your mouse to a single notification. Middle-clicking on an app’s name will dismiss all the notifications listed for that app.

Apps for websites: As we discussed at Build 2016, you will soon be able to redirect certain websites to open with an app instead. While there are currently no apps that support this, in preparation for their availability we have added a new page at Settings > System > Apps for websites where you will be able to manage them. Please stay tuned!

Feedback Hub improvements: We’ve heard from you that it can sometimes be hard to find which category your feedback belongs in. Now when you create new feedback, the Feedback Hub will suggest categories and subcategories based on the title and description you entered. If you see a suggestion that looks right, just click it to fill in the menus and get your feedback to the right engineers quickly.

Here’s what’s fixed for PC

  • We have fixed the issues blocking the Desktop App Converter Preview (Project Centennial). You can now run the converter on the Enterprise edition as well as Pro edition of Windows. You will need the latest converter and base image from here to take advantage of all the improvements which will be available later today.
  • We fixed the issue causing Tencent online games from not working in current builds from the Development Branch.
  • We have fixed the issue causing DRM-protected content from services like Groove Music, Microsoft Movies & TV, Netflix, Amazon Instant Video or Hulu from being playable with playback with 0x8004C029 or 0x8004C503 errors.
  • We fixed an issue resulting in audio crashes for users who play audio to a receiver over S/PDIF or HDMI, and use a driver that supports real-time encoding via technologies like Dolby Digital Live or DTS Connect.
  • Polished the animation when invoking Cortana on the Lock screen. And also resolved an issue where tapping the link to fix mic issues wouldn’t fix them.
  • We fixed an issue resulting in the ok/cancel buttons in the network flyout being clipped on high DPI devices.
  • We fixed an issue where you might see Windows Hello messages on the screen while you were already logging in with a fingerprint.
  • We fixed the issue where if you were in an app and clicked on a link with a URL longer than 260 characters, it would bring up the “Open with…” dialog instead of opening with your default browser.
  • We fixed an issue resulting in not being able to use your mouse in the Photos app to either move photo while zoomed or adjust crop region.
  • The ALT + Y keyboard shortcut to choose “yes” now works with the updated UAC UI.
  • Updated new Credential UI to add support for pasting into username and password fields
  • Polished icons used to identify pages in the Settings app – in particular, updated battery icon to be more consistent with the weight of the other icons.
  • Made some polish improvements to the Action Center, and resolved an issue where icon in Taskbar wasn’t displaying correctly at 175% DPI.
  • We fixed an issue where the image used in Screen Sketch would be rotated 90 degrees for native portrait devices (such as the Dell Venue 8 Pro). Also polished the experience of cropping images in Screen Sketch.
  • We fixed Clock and Calendar flyout issues on the taskbar with the 24-hour time format where the agenda items would display using 12-hour format instead of the 24-hour time format and certain items would be off by 12 hours.
  • We fixed an issue where the Clock and Calendar flyout couldn’t be dismissed by clicking on the date and time in the taskbar a second time.
  • We updated the “set location” notification so tapping anywhere in the notification will now enable you to set a default location.
  • We fixed an issue where certain shortcuts weren’t working in UWPs, for example CTRL + C, CTRL + V, and ALT + Space.
  • We fixed an issue where tapping the battery icon wouldn’t open the Battery flyout when in Tablet Mode.
  • We fixed an issue where clicking elements in the Start navigation pane might result in the Store opening instead.
  • We fixed an issue where background audio tasks might show up in the volume controls.
  • We added a “Clear Input History” option to the IME Settings page.
  • We fixed an issue where doing an action on a file in a folder pinned to Quick Access after using the address bar to get there might result in File Explorer unexpectedly navigating to Quick Access.
  • We fixed an issue resulting in Cortana crashing if you shared an avatar with Cortana from the Xbox Avatars app.
  • We fixed an issue causing the search box on the Language Settings page to not work.

Known issues for PC

  • Feedback Hub is not localized and the UI will be in English (U.S.) only, even with language packs installed.
  • Feedback Hub takes about 20-30 minutes after updating to this build to download and populate itself if launched from Start. If you launch Feedback Hub from All apps – it will force the app to hydrate.
  • Symantec products such as Norton Antivirus and Norton Internet Security are causing PCs to bluescreen (bug check).
  • The QQ app from Tencent crashes. We’re working on a fix for the issue.
  • If you are using a non-English keyboard, you can’t accept Bash prompts.
  • We are investigating an issue where if you’re running Insider Preview builds in certain languages, the All apps list on Start appears empty. A workaround for this is to use search to launch apps.
  • You may see square boxes in certain apps when using some of the new emoji – we’re still getting things set up, this will be resolved in a future build.

Other items of note

We have removed the Wi-Fi Sense feature that allows you to share Wi-Fi networks with your contacts and to be automatically connected to networks shared by your contacts. The cost of updating the code to keep this feature working combined with low usage and low demand made this not worth further investment. Wi-Fi Sense, if enabled, will continue to get you connected to open Wi-Fi hotspots that it knows about through crowdsourcing.

As always – thank you for being Windows Insiders and make sure to send us feedback on any issues you run into with these builds in the Feedback Hub.


13" MacBook Pro Retina 2015 (i5 2.9GHz / 8GB RAM / 512GB SSD) – £950!

I have for sale a 13″ MacBook Pro Retina 2015 (i5 2.9GHz / 8GB RAM / 512GB SSD).

This is the latest model with the Force Touch touchpad.

Comes boxed as new in mint condition.

Battery cycle count is around 5 as it’s been barley used.

Price and currency: £950
Delivery: Delivery cost is not included
Payment method: Bank Transfer…

13″ MacBook Pro Retina 2015 (i5 2.9GHz / 8GB RAM / 512GB SSD) – £950!

Getting started storing app data locally

When thinking about your app data, one aspect to consider is data lifetime. In general, when it comes to the lifetime of data, you have two options: local data, which exists as long as the app that created it remains installed, and roaming data, that will continue existing online even after your app is uninstalled. If you want your data to be roamed/synced and live independently of a single app installation you have different options available, such as the roaming app data feature discussed in the recent blog post series on that topic or by using a cloud data provider, such as OneDrive or Azure.

In today’s blog post, we will talk about local data, or data that is tied to the specific device where it was created. We will be looking at the different features that the Universal Windows Platform provides you with to do this, examples, and best practices.

Types of app data

There are two types of app data: settings and files.

  • Settings. Use settings to store app state and user preferences. The Universal Windows Platform (UWP) provides APIs to easily store and retrieve settings. The data types you can use in app settings are:
  • Files. Use files to store binary data or to serialize your own custom types.

Storing app data locally

When an app is installed, the system creates a per-user app data container on the device. This app data container is within the app sandbox, which means no other app will be able to access it. The system will preserve the content of the data container when the app is updated and will remove it when the user uninstalls the app.


As a developer, you have three locations available in the app data container to store data locally:


Local can contain both files (LocalFolder) and settings (LocalSettings) and should be used for any information that is of user value and can’t easily be recreated or downloaded. Data stored in Local can be backed up by the system if the device supports App Data Backup. Because of this, you should avoid using Local to store cached or temporary files that you could create or fetch again on demand.


App Data Backup

During a device backup operation, the system will grab any app data in Local and store it as part of a device backup image in OneDrive. If the user resets or replaces the device, he or she will be given the choice to restore a previous backup, which will restore the app data in Local as part of the app’s installation. Note that by not storing data in Local you will effectively be opting out of backup for your app.

Best practices for Local

  1. Use for data with user value that can’t be recreated or downloaded by your app. If you place cached content or throwaway data in Local you are wasting user storage on OneDrive and delaying how long it takes to install your app during a device restore.
  2. Use for settings that are unique to a device. In general, it is desirable to have common user settings on all of the user’s devices. However if you have settings that you don’t want roamed you should store them in Local.
  3. Do not store credentials in Local. In order to offer the best user experience around credentials you should be using the Credential Locker feature.
  4. Avoid it for data tied to specific hardware. If you have data that can only be consumed on the same physical device where it was created do not place in Local, because the user may choose to restore this data to a different device. One example of data tied to specific hardware is anything derived from device ID.

Using LocalFolder

To read or write files in LocalFolder, you must use the ApplicationData.LocalFolder property; you will get back a StorageFolder. You can then use StorageFolder.CreateFileAsync and StorageFolder.GetFileAsync to write and read files.

//Create dataFile.txt in LocalFolder and write “My text” to it 
StorageFolder localFolder = ApplicationData.Current.LocalFolder;
StorageFile sampleFile = await localFolder.CreateFileAsync("dataFile.txt");
       await FileIO.WriteTextAsync(sampleFile, "My text"); 

       //Read the first line of dataFile.txt in LocalFolder and store it in a String
       StorageFile sampleFile = await localFolder.GetFileAsync("dataFile.txt");
       String fileContent = await FileIO.ReadTextAsync(sampleFile);

Using LocalSettings

To read or write settings in LocalSettings, you must use the ApplicationData.LocalSettings property; you will get back an ApplicationDataContainer. You can then access the content of LocalSettings through the Values property.

//Check if setting #postsToDownload exists and create it if it does not
       ApplicationDataContainer localSettings = ApplicationData.Current.LocalSettings;
       var value = localSettings.Values["#postsToDownload"];
       if (value == null)
       	localSettings.Values["#postsToDownload"] = 5;


Use LocalCache to store app data that you want persisted across app sessions, but that should not be backed up by the system. LocalCache is the right place for data with the same lifetime as your app and that can be easily recreated or downloaded as needed.

Best practices for LocalCache

  1. Use it for cached or generated content you need across app sessions. If you are downloading online files, LocalCache is probably the right place for them.
  2. Use it for authentication tokens. Authentication tokens should not be backed up and LocalCache is generally the right location for them.

Using LocalCache

LocalCache can only contain files and is accessed through the ApplicationData.LocalCacheFolder property.

//Create dataFile.txt in LocalCacheFolder and write “My text” to it 
StorageFolder localCacheFolder = ApplicationData.Current.LocalCacheFolder;
      	StorageFile sampleFile = await localCacheFolder.CreateFileAsync("dataFile.txt");
     	await FileIO.WriteTextAsync(sampleFile, "My text");

//Read the first line of dataFile.txt in LocalCacheFolder and store it in a String
       StorageFile sampleFile = await localCacheFolder.GetFileAsync("dataFile.txt");
       String fileContent = await FileIO.ReadTextAsync(sampleFile);


As the name suggests, the Temporary App Data store is the right place for data that you don’t want persisted after the current app session. The system can delete data stored at this location as needed to free up space.

Best practices for Temporary

  1. Use Temporary for any intermediate or temporary files. If you won’t need a file after your app is terminated or suspended, this is the right location for it.
  2. Clean your Temp folder during app initialization. If you are writing large amounts of data to Temp, it is a good idea to clear it when your app is initialized to avoid the system or the user having to take action to free up storage.

Using the Temporary App Data store

Use ApplicationData.TemporaryFolder to get a StorageFolder and access the Temporary App Data store. You can then use the different StorageFolder methods to write and read files.

//Create dataFile.txt in TemporaryFolder and write “My text” to it 
StorageFolder tempFolder = ApplicationData.Current.TemporaryFolder;
StorageFile sampleFile = await tempFolder.CreateFileAsync("dataFile.txt");     await FileIO.WriteTextAsync(sampleFile, "My text");

//Read the first line of dataFile.txt in Temp and store it in a String
       StorageFile sampleFile = await tempFolder.GetFileAsync("dataFile.txt");
       String fileContent = await FileIO.ReadTextAsync(sampleFile);

Wrapping Up

In this post, we have provided you with an introduction to storing app data locally as well as examples and best practices. Hopefully, you’ll be able to use this information to create experiences that delight your users.

Additional Resources

Written by Hector Barbera, Program Manager for Developer Ecosystem and Platform

Z68/Z77 ITX Motherboard

I’m considering building a new gaming HTPC, I have a 2500K (which I’ve owned since release) but never overclocked it. Does anyone have a spare Z68/Z77 ITX motherboard they’re happy to sell for a reasonable amount?

I have noted that eBay auctions can go for ludicrous figures, something I’m not at all interested in.

Location: Coventry, UK

This message is automatically inserted in all classifieds…

Z68/Z77 ITX Motherboard