Category Archives: PC

Auto Added by WPeMatico

Introducing the Storage Access API – Microsoft Edge Blog

Today, we’re excited to announce the “first-look” rollout of the Storage Access API in our Canary and Dev channels. For developers, this API allows them to determine whether their access to browser-based storage is restricted by a user’s privacy settings and to request storage access from users if so. This capability can be used to create graceful fallback experiences in cases when storage access may be restricted by features such as tracking prevention in Microsoft Edge. For users, this API provides greater transparency into and control over the sites that are requesting access to browser-based storage that could be used to track their behaviors across the web. This post outlines what the addition of the Storage Access API means for both developers and users.

Using the Storage Access API is as easy as updating your code to leverage the following new functions:
hasStorageAccess()
Useful to check if access to cookies and other storage exists in the current context.
Returns a promise with a boolean result indicating if storage access exists or not.

requestStorageAccess()
Requires a user gesture to invoke.
Useful to request access to storage for a single third-party context.
Returns a promise that will resolve if access is either available or granted and reject if unsuccessful.

Note: Since we are still gradually rolling out the Storage Access API, it’s possible that you may not have it enabled by default on your device. If you want to test it early, please enable the “Storage Access API” flag in edge://flags.
The usage of these new functions is best demonstrated with an example.
Example:
A social media site, contoso.social, offers sites the ability for developers to embed social media widgets as third-party content on their sites. One site where these widgets appear is www.contoso.example. To offer the ability for contoso.social users to comment on, save, or share contoso.example content with friends, contoso.social’s embedded content needs access to its own storage such as cookies or localStorage in the context of contoso.example in order to associate these actions with a visitor’s account.
Checking for Access:
contoso.social can use document.hasStorageAccess() to see if access to storage already exists and to provide an alternative user experience such as displaying a request to login or request access if not:

Requesting Access:
If no storage access is currently present, contoso.social can request access during a user gesture. As an example, the onclick handler of a login button could be tied to a request for storage access (see the “User Experience” section below) using the document.requestStorageAccess() method.

Sandboxing
The allow-storage-access-by-user-activation token can be used to enable the usage of the API when embedded content is loaded in a sandboxed iframe. In practice, both the allow-scripts and allow-same-origin tokens will also be required as well to ensure the API can be effectively used.

As a developer, we hope you will leverage the Storage Access API to create web-based experiences that will continue to be compatible even as browsers place more restrictions on third-party storage.

With the introduction of the Storage Access API, you may notice an “Allow cookies and site data?” prompt like the one below when you interact with third-party content such as social media widgets or embedded videos while browsing:

This indicates that the site whose embedded content you’re interacting with (contoso.social in the example above) currently has its storage restricted by Microsoft Edge’s privacy settings and is requesting your permission to access its storage within the context of the site you’re visiting (https://www.contoso.example in the example above). While several types of sites require storage access for legitimate scenarios such as making sure you’re signed in when you expect to be, allowing this access can allow the site requesting it track your activity on the site you’re currently visiting.
Clicking “Allow” will temporarily allow the requesting site access to its storage on the site you were visiting when the prompt appeared. This allowance will last for a 30-day period after which it will automatically expire. Clicking “Block” will prevent the requesting site from accessing its storage on the site you were visiting when the prompt appeared. If you change your mind, interacting with the third-party content a second time will cause the prompt to be displayed again, giving you the option to revisit your choice.
To give you control over any storage access requests you’ve allowed before they automatically expire, you’ll notice a new “Cookies and site data you’ve temporarily allowed” section at the bottom of the edge://settings/content/cookies page. Here, you can review and revoke the storage access requests you’ve granted in a single list:

We implemented the Storage Access API upstream so that all Chromium-based browsers could benefit from it. We are also actively participating in standardization discussions that are ongoing in the W3C Privacy Community Group to ensure that the API works uniformly across browsers. If you have any feedback on the functionality or capabilities of the API itself, please feel free to join the standardization discussions by filing an issue on GitHub. If you have any feedback on the Storage Access API as it exists in Microsoft Edge, please send us feedback using in-app feedback tool (Alt + Shift + I).
To close, we’d like to thank our friends at Apple and Mozilla for their early work on the Storage Access API and our friends at Google for helping pave the way for getting the API implemented in Chromium. We’re excited for you to try it out and to hear what you think!
–  Brandon Maslen, Senior Software Engineer–  Scott Low, Senior Program Manager

A deep-dive into WinUI 3 in desktop apps – Windows Developer Blog

XAML Islands was our first solution to enable developers to use UWP XAML inside their desktop (Win32) apps. Within a couple of months after the release of XAML Islands, behavioral insights and customer interviews raised some signals about how developers were using it. We discovered that a significant number of apps were using XAML for the entire UI; in fact, many apps were using WPF’s Window and Windows Forms’s Form classes for the sole purpose of hosting XAML. Additionally, interviews revealed that C++ Windows developers were interested in XAML as a replacement for MFC.
This made us think about whether we can help customers further. We listed a set of hypotheses about what Windows developers were expecting and created a prototype to validate/invalidate these hypotheses. The outcome of this validation process was very enlightening. Windows developers were hungry for creating beautiful, modern, and refreshing apps reusing the desktop code (in the form of .NET or C++ Win32) that they had already been using. In most cases, this code needed to run outside of the security sandbox (AppContainer) and work in all versions of Windows 10 in the market. So we extended WinUI 3 to support desktop apps in addition to UWP apps. WinUI 3.0 Preview 1 introduced project templates to create desktop C# .NET 5 apps and C++ 17 desktop apps where the entire user interface is implemented using windows, controls, and other UI elements provided by the WinUI framework.
But enough of so much chatter and let’s get to work! In this blog post I’m going to focus on building a desktop app with WinUI 3 Preview 1 and .NET, leaving C++ for future posts.
The first step is to install WinUI3 Preview 1 (or Preview 2 when available) in your development machine. I recommend visiting this link and following the Prerequisites instructions to download and install the VSIX that contains the project templates. After that, follow the instructions to create a WinUI 3 desktop app for C# and .NET 5. Press F5 and you will see something like this:

There are a lot of things that you can learn from this project without writing a line of code. The first noticeable thing is that there are two projects in the solution. One is for the Desktop WinUI 3 app itself, and the other is for packaging the app into a MSIX. In Preview 1 it’s required to package your project to run your app. Although MSIX is our recommended packaging technology, we’re aiming to make a UI Framework that’s independent of the deployment mechanism. This is a temporary limitation that we will address in subsequent previews , as you can see in the Preview 1 known issues documentation.

Embracing .NET 5
If you double click on the WinUI 3 app project, Visual Studio opens the project file with the XML text editor, and you can observe several things. First, C# Desktop WinUI 3 projects embrace the SDK-style project so it’s human readable/understandable. Second, the Target Framework is .NET 5. Desktop WinUI 3 can be used with the next big release in the .NET family. Third, you can see that this project has a reference to the Microsoft.WinUI NuGet package, which pulls in the WinUI 3 tools and runtime.

<Project Sdk=”Microsoft.NET.Sdk”>
<PropertyGroup>
<OutputType>WinExe</OutputType>
<TargetFramework>netcoreapp5.0</TargetFramework>
<TargetPlatformVersion>10.0.18362.0</TargetPlatformVersion>
<TargetPlatformMinVersion>10.0.17134.0</TargetPlatformMinVersion>

<Platforms>x86;x64</Platforms>
<SelfContained>true</SelfContained>
<RuntimeIdentifiers>win-x86;win-x64</RuntimeIdentifiers>
<RuntimeIdentifier>win-$(Platform)</RuntimeIdentifier>
</PropertyGroup>

<ItemGroup>
<PackageReference Include=”Microsoft.VCRTForwarders.140″ Version=”1.0.6″ />
<PackageReference Include=”Microsoft.WinUI” Version=”3.0.0-preview1.200515.3″ />
</ItemGroup>

</Project>

Speaking of tools, WinUI 3 uses the new C#/WinRT projections. The WinUI 3 framework is a set of WinRT components, and while WinRT has similar types and objects as those found in .NET, they are not inherently compatible. The C#/WinRT projections handle the interop between .NET and WinRT, allowing you to freely create and use WinUI objects in your .NET app today.
The WinUI 3 NuGet package has a dependency on the C#/WinRT NuGet package which brings the winrt.runtime.dll library and the cswinrt.exe tool. The cswinrt.exe tool consumes WinMD metadata files that define the WinRT libraries and generates interop .NET 5 and .NET Standard 2.0 C# code. This interop code uses the winrt.runtime.dll library. As you can guess, the cswinrt.exe gets all the WinUI WinMD files and generates C# interop code .NET 5 code for the WinUI library. Then you can compile these files into a .NET library (e.g. using the csc.exe compiler) and use it in every .NET 5 Desktop WinUI application. Fortunately, we already have created this library for you. It’s the Microsoft.WinUI.dll library. This library is included in the WinUI 3 NuGet Package.

The WinUI NuGet package also has a dependency on the Microsoft.Windows.SDK.NET NuGet package. This package includes the Microsoft.Windows.SDK.NET.dll  .NET 5 (and .NET Standard 2.0) interop  library  that allows use of the other non-WinUI WinRT APIs that are available as part of the Windows 10 OS. Like Microsoft.WinUI.dll, this DLL is generated by C#/WinRT.
Window class and Win32 APIs
With WinUI 3 Preview 1, you can create instances of the Window class in XAML markup. Double click on the MainWindow.xaml file and you will see an example of this:

<Window
x:Class=”HelloWorldDesktopWinUI3CS.MainWindow”
xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/presentation”
xmlns:x=”http://schemas.microsoft.com/winfx/2006/xaml”
xmlns:local=”using:HelloWorldDesktopWinUI3CS”
xmlns:d=”http://schemas.microsoft.com/expression/blend/2008″
xmlns:mc=”http://schemas.openxmlformats.org/markup-compatibility/2006″
mc:Ignorable=”d”>

<StackPanel Orientation=”Horizontal” HorizontalAlignment=”Center” VerticalAlignment=”Center”>
<Button x:Name=”myButton” Click=”myButton_Click”>Click Me</Button>
</StackPanel>
</Window>

The XAML Window class was extended to support desktop windows, turning it into an abstraction of the low-level window implementation used by each app model. For instance, the UWP app model uses CoreWindow, while the Win32 app model uses Win32 window handles (HWND). So if you’re building a Desktop WinUI app, you can get the window handle and use Win32 APIs with it.
For example, let’s maximize the Window programmatically using the classic User32 ShowWindow API. To call Win32 APIs from User32.dll you can use the NuGet package PInvoke.User32. Once you have added it, open the code-behind of MainWindow.xaml.cs and add these lines to the button event handler:

private void myButton_Click(object sender, RoutedEventArgs e)
{
myButton.Content = “Clicked”;

IntPtr hwnd = (App.Current as App).MainWindowWindowHandle;
PInvoke.User32.ShowWindow(hwnd, PInvoke.User32.WindowShowStyle.SW_MAXIMIZE);

}

The ShowWindow method uses the window handle and maximizes it using the second parameter. To get the window handle you can use the GetActiveWindow method that returns the window handle of the current active Window. For example, you can call this method after activating the Window.
The MainWindow object is created, instantiated, and activated in the OnLaunched event that you can find in the App.xaml.cs.

IntPtr m_windowhandle;
public IntPtr MainWindowWindowHandle { get { return m_windowhandle; } }
protected override void OnLaunched(Microsoft.UI.Xaml.LaunchActivatedEventArgs args)
{
m_window = new MainWindow();
m_window.Activate();
m_windowhandle = PInvoke.User32.GetActiveWindow();
}

To show the window and the focus you need to call Activate. Easy, right?
Like we did within the Window class, we also extended the Application class to support both UWP and Win32 app models. The Application object is aware of whether the runtime environment is Win32 or UWP, and fires the appropriate application life cycle events. For example, the Resuming event is never fired in Win32 but is in UWP.
Full trust desktop apps
I mentioned earlier that developers want their code to be able to run outside of the security sandbox without any AppContainer – this is called “full trust permission” in the WinRT jargon – and Desktop WinUI 3 allows them to do so. You can call all the .NET 5 APIs without restrictions. For instance, you can query the current process and get a list of its loaded modules; this is something you can’t do in the UWP app model. Let’s see how easy it is:
In the MainWindow.xaml create a ContentDialog:

<StackPanel Orientation=”Horizontal” HorizontalAlignment=”Center”
VerticalAlignment=”Center”>
<Button x:Name=”myButton” Click=”myButton_Click”>Click Me</Button>
<ContentDialog x:Name=”contentDialog”
Title=”Loaded modules”
CloseButtonText=”OK”>
<ScrollViewer MaxHeight=”800″>
<TextBlock x:Name=”cdTextBlock” TextWrapping=”Wrap” />
</ScrollViewer>
</ContentDialog>
</StackPanel>

And in the code-behind of MainWindow.xaml.cs call the .NET APIs from System.Diagnostics to get the modules loaded in a process:

private async void myButton_Click(object sender, RoutedEventArgs e)
{
myButton.Content = “Clicked”;

var description = new System.Text.StringBuilder();
var process = System.Diagnostics.Process.GetCurrentProcess();
foreach (System.Diagnostics.ProcessModule module in process.Modules)
{
description.AppendLine(module.FileName);
}

cdTextBlock.Text = description.ToString();
contentDialog.XamlRoot = myButton.XamlRoot;
await contentDialog.ShowAsync();

}

Press F5 to Run and you will get something like this picture when clicking the button:

I have shown you a lot of things with just a few lines of code. .NET with WinUI 3 in Desktop apps allows you to use the .NET APIs as you expect (no limitations) while using WinUI 3 as your UI Framework. Getting access to the underlying window implementation, in this case Win32 and HWNDs, enables you to use the vast set of Win32 APIs in your app in addition to the WinRT APIs of Windows 10. This will allow you to create new Desktop WinUI 3 apps reusing the majority of your current code.
You can get more samples of WinUI 3 in desktop here, and you leave feedback on our Github repo.
Happy WinUI coding devs! 
Miguel Ramos – WinUI/XAML PM
Twitter: @marbtweeting
GitHub: @marb2000

Announcing Windows 10 Insider Preview Build 20161 | Windows Experience Blog

Hello Windows Insiders, today we’re releasing Windows 10 Insider Preview Build 20161 to Windows Insiders in the Dev Channel.
A few quick notes:
First—as a reminder, these builds are from our Active Development Branch and are not tied to any upcoming Windows 10 release. Insiders in the Dev Channel are getting the latest code from our engineers.
Second—we have officially rolled out channels to the Windows Insider Program Settings page, If you haven’t already, check out our blog post here outlining the transition from rings to channels.
And third—we’re introducing some cool new features in today’s build, however many of these features are rolling out to a subset of Insiders in the Dev Channel at first, to help us quickly identify issues that may impact performance and reliability. This means Insiders may not see some of these features right away, but rest assured they will be gradually rolled out to everyone in the Dev Channel. Check out what the team has been working on!

Theme-aware tiles in Start
We are freshening up the Start menu with a more streamlined design that removes the solid color backplates behind the logos in the apps list and applies a uniform, partially transparent background to the tiles. This design creates a beautiful stage for your apps, especially the Fluent Design icons for Office and Microsoft Edge, as well as the redesigned icons for built-in apps like Calculator, Mail, and Calendar that we started rolling out earlier this year.

This refined Start design looks great in both dark and light theme, but if you’re looking for a splash of color, first make sure to turn on Windows dark theme and then toggle “Show accent color on the following surfaces” for “Start, taskbar, and action center” under Settings > Personalization > Color to elegantly apply your accent color to the Start frame and tiles.

Want the amazing desktop background shown in the screenshot above? Download our ‘Pride 2020 Flags’ theme from the Microsoft Store!
ALT + TAB between apps and sites
Are you a multitasker? We have exciting news for you! Beginning with today’s build, all tabs open in Microsoft Edge will start appearing in Alt + TAB, not just the active one in each browser window. We’re making this change so you can quickly get back to whatever you were doing—wherever you were doing it.

If you’d prefer fewer tabs or the classic Alt + TAB experience, we’ve added some settings for you under Settings > System > Multitasking. You can configure Alt + Tab to only show your last three or five tabs or choose to turn this feature off completely.
This feature is currently rolling out to a subset of Insiders today in the Dev Channel and requires a Canary or Dev build of Microsoft Edge (version 83.0.475.0 or higher).
This is just the beginning of productivity enhancements coming to Microsoft Edge—stay tuned!
A more personalized Taskbar for new users
We want to help customers get the most out of their PCs from day one, and that starts with offering a cleaner, more personalized, out-of-box experience to give you the content you want and less clutter. This provides us with a flexible, cloud-driven infrastructure to test customer reception of default Taskbar content and tailor these layouts based on user and device signal.
We will evaluate the performance of individual default properties, monitoring diagnostic data and user feedback to assess an audience’s reception. Using this information, we will tune default layouts to minimize clutter and perceptions of bloatware.
Please note that this experience is limited to new account creation or first logon scenarios. We will not use Programmable Taskbar to alter the Taskbar layout on existing accounts.

Improving the notification experience
We are making some changes to improve the notifications experience in Windows 10.
First, know where your toast is coming from by checking out the app logo at the top. Done with the notification? Select the X on the top right corner to quickly dismiss and move on with your life.

And second, we are turning off the Focus Assist notification and summary toast by default, so we will no longer let users know that Focus Assist has been turned on through an automatic rule via a notification. This can be changed back to the previous behavior via Settings.
Making Settings even better
We’re continuing to work on bringing capabilities from Control Panel forward into Settings. As part of this ongoing effort, we are migrating information found in Control Panel’s System page into the Settings About page under Settings > System > About. Links that would open the System page in Control Panel will now direct you to About in Settings. We are also bringing new improvements like making your device information copyable and streamlining the security information shown. And don’t worry—if you’re looking for more advanced controls that lived in the System page in Control Panel, you can still get to them from the modern About page if you need them!

There will be more improvements coming that will further bring Settings closer to Control Panel. If you rely on settings that only exist in Control Panel today, please file feedback and let us know what those settings are.
Improving the tablet experience for 2-in-1 devices
Previously, when detaching the keyboard on a 2-in-1 device, a notification toast would appear asking if you wanted to switch into tablet mode. If you selected yes, you would switch into tablet mode. If you chose no, it would give you the new tablet posture experience introduced in the May 2020 Update (or simply the desktop on earlier versions of Windows 10). We are further updating this experience by changing the default, so that this notification toast no longer appears and instead will switch you directly into the new tablet experience, with some improvements for touch. You can change this setting by going to Settings > System > Tablet. Some users may have already seen this change on Surface devices.
And to address confusion with some users getting stuck in tablet mode on non-touch devices, we are removing the tablet mode quick action on non-touch devices.
In addition, new logic is incorporated to let users boot into the appropriate mode according to the mode they were last in and whether the keyboard is attached or not.

Windows Calculator graphing mode feature now rolling out to the public
We are happy to announce that the graphing mode feature we released to Insiders in January is now rolling out to the general public! Adding support for graphing was one of our top feature requests, so we’re excited to bring this feature to our users. Graphing capabilities are also essential for students who are beginning to explore linear algebra. With this feature, we hope to empower students to learn mathematics by improving their conceptual understanding and attitudes towards math.

Key features
Plot one or more equations on the graph. Enter multiple equations so that you can compare plots against each other and see interactions between the lines.
Add equations with variables. If you enter equations with variables (e.g., y = mx + b), you’ll be able to update the value of those variables to see the changes live on the graph.
Analyze the graph. Trace plots with your mouse or keyboard and analyze equations to help identify key graph features, like the x- and y-intercepts.

Since we released the feature in preview earlier this year, we’ve made lots of improvements based on your feedback in Feedback Hub and on GitHub, like introducing a brand new dark theme graph and more line customization options, adding error handling for when you try to plot an equation that isn’t quite right, and improving the overall experience when tracing or plotting multiple equations at the same time.
Thank you for your feedback and helping to make this feature better for everyone! You must have the Windows 10 May 2020 update and the latest version of Windows Calculator to access this feature.

The Windows SDK is now flighting continuously with the Dev Channel. Whenever a new OS is flighted to the Dev Channel, the corresponding SDK will also be flighted. You can always install the latest Insider SDK from aka.ms/InsiderSDK. SDK flights will be archived in Flight Hub along with OS flights.

We fixed an issue resulting in Insiders experiencing bug checks when connecting and interacting with an Xbox controller.
We’ve fixed an issue causing some games and applications to crash at launch or fail to install.
We fixed an issue resulting in Microsoft Edge not navigating to websites when WDAG was enabled on the last 2 flights.
We fixed an issue which was increasing log off time in recent builds.
We fixed an issue with the Chinese Pinyin IME where after setting your preferred IME toolbar orientation, you may not be able to change it again after rebooting your PC.
We fixed an issue causing Reset this PC to always show the error “There was a problem resetting this PC” when launched from Settings in the last few builds.
We fixed an issue resulting in some Bluetooth devices no longer showing their battery level in Settings in the last few builds.
We fixed an issue where Settings would crash if you went to Settings > Privacy > Microphone while a win32 app was recording audio.
We fixed an issue where if Sound Settings showed “no input devices found” in the input dropdown and you clicked it, then Settings would crash.
We fixed an issue where when adding a printer, the dialog might crash if you navigated through to the “Add a printer driver” dialog in recent builds.
We fixed a graphics related issue resulting in some users experiencing bugchecks.

We’re working on a fix for an issue causing some systems to crash with a HYPERVISOR_ERROR bugcheck.
We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
We’re aware of an issue where Notepad might fail to reopen files which were automatically saved during a PC restart (if that option is enabled in Settings). Documents can be recovered from %localappdata%Notepad.We’re investigating reports of the screen becoming dimmer after upgrading to the previous build.
We’re aware of an issue where Task Manager reports 0.00 GHz CPU usage in the Performance tab.
We’re investigating reports that when you press space while using the Korean IME in certain apps, the last character is deleted.
We’re working to fine tune the tile animations in Start to avoid flashes of color.
For Insiders with the new Alt+Tab experience mentioned above, please note that the setting under Settings > System > Multitasking to set Alt+Tab to “Open windows only” currently doesn’t work.

Today, we launched a redesigned version of the Windows Insider website that’s build with Microsoft’s new, more accessible framework. This was an important chance to align our site with improvements Microsoft is making across the board, create a more beautiful and user-friendly home for the program, and better highlight all the ways you can engage with us.
Right now, the site is only available in the en-us English language while we also stand up new and improved translated versions of the site. Thank you for your patience as we try to make this website work better for Insiders around the world.
If you speak English, please go take a look. We’re also implementing new tools that will help us improve the site based on how you all are using it, so the more you explore the better. If you have any issues, reach out to us @WindowsInsider on Twitter.

As a reminder, some of the features mentioned above for this build are being rolled out to a subset of Insiders in the Dev Channel at first. If you don’t see some of the features right away, please be patient as we’ll be rolling them out to more Insiders in the Dev Channel over time.
You can check out our Windows Insider Program documentation here, including a list of all the new features and updates released in builds so far. Not seeing any of the features in this build? Check your Windows Insider Settings to make sure you’re in the Dev Channel. Submit feedback here to let us know if things weren’t working the way you expected.
If you want a complete look at what build is in which Insider ring, head over to Flight Hub. Please note, there will be a slight delay between when a build is flighted and when Flight Hub is updated.
Thanks,BLB

Now available: Jungle Awakens, Minecraft Dungeons’ first DLC pack | Windows Experience Blog

If you’ve been waiting for Minecraft Dungeons’ first DLC pack, it’s now available for Windows and Xbox One: Jungle Awakens.
This update features everything from new missions and game mechanics, to never before seen mobs and items – as well as a unique challenge.
You’ll get extra content for the Minecraft Dungeons base game – free of charge: a map to the Lower Temple, a new threat level per difficulty and new gear. Download by updating the game.
To get the new DLC, you can either buy it separately for your platform or upgrade your Standard Edition with a Hero Pass (and by doing so, securing yourself the first two DLC packs).
Minecraft has all the details.

New computers: why get one now and what to look for | Windows Experience Blog

What with the huge growth in video calling and the fact many of us spend a lot more time using our tech devices to stay connected, entertained and educated, yesterday’s computers often just don’t do the trick anymore.
If you’re on the fence about whether now is the time to replace your computer and what features you should look for if you do, head over to the Windows Home and Family Resources Blog. There you’ll find three main reasons to upgrade, what processor to choose based on your needs and budget, the best drive for you and more.

3 Ways to Customize Your Windows Terminal – Windows Developer Blog

Windows Terminal is here! From the buzz of the announcement at Microsoft Build 2019 to the release of 1.0 at Build 2020, it’s generated excitement and interest from the dev community. Get started by downloading the Preview here.
As a refresher, Windows Terminal is a new, modern, fast, efficient, powerful, and productive terminal application for users of command-line tools and shells like Command Prompt, PowerShell, and WSL.
Its main features include multiple tabs, panes, Unicode and UTF-8 character support, a GPU accelerated text rendering engine, and the ability to create your own themes and customize text, colors, backgrounds, and shortcut key bindings.
Today, we’re digging into three ways to tailor the Terminal to your preference: colors, cursor, and tabs.

Windows Terminal includes the following named color schemes inside the defaults.json file, which can be accessed by holding alt and selecting the settings button.
Campbell
Campbell Powershell
Vintage
One Half Dark
One Half Light
Solarized Dark
Solarized Light
Tango Dark
Tango Light
This is what Vintage looks like:
To set up your scheme inside one of your command-line profiles, add the colorScheme property with the color scheme’s name as the value.
“colorScheme”: “COLOR SCHEME NAME”
Every setting, aside from name, accepts a color as a string in hex format: “#rgb” or “#rrggbb”. The cursorColor and selectionBackground settings are optional.
Dark and light theme are also available in the Terminal’s chrome.
Property name: theme
Necessity: Optional
Accepts: “system”, “dark”, “light”
Default value: “system”

Old school or modern, there’s a full set of cursor options for shape, color, and height.
Do you prefer horizontal or vertical? A line or a box? Just tell the Terminal.
This sets the cursor shape for the profile. The possible cursors are as follows: “bar” ( ┃ ), “vintage” ( ▃ ), “underscore” ( ▁ ), “filledBox” ( █ ), “emptyBox” ( ▯ )
Property name: cursorShape
Necessity: Optional
Accepts: “bar”, “vintage”, “underscore”, “filledBox”, “emptyBox”
Default value: “bar”
You can override cursorColor set in the color scheme if colorScheme is set. Color as a string in hex format: “#rgb” or “#rrggbb” are accepted.
cursorHeight sets the percentage height of the cursor starting from the bottom. This will only work when cursorShape is set to “vintage.” Integers from 25-100 are accepted.

You can easily rename and recolor tabs in Windows Terminal Preview. Just right click on a tab and select Rename Tab to rename a tab for that session. This option will change your tab title into a text field, where you can then edit the title.
Do the same to recolor your tab. Select from a predefined list of colors or click Custom to use the color picker or the RGB/HSV or hex fields. One cool tip is to use the hex field to set your tab to the same color as your background color for a seamless look.

To set the tab title for a profile for every terminal instance, check out the Tab title tutorial.
Monthly updates for Windows Terminal begin in July 2020. Don’t forget to download Windows Terminal Preview from the Microsoft Store or from the GitHub releases page. This is the channel where you can be involved with the development of Windows Terminal and use the latest features as soon as they are developed.

Check out ‘Simply Windows’ to find out how to get more organized using Microsoft Edge | Windows Experience Blog

The latest “Simply Windows” video is now available, focusing on tips for organizing your tabs in Microsoft Edge.
If you’re new to Windows 10 or want to learn more about how to get the most out of it, this video series can help you get up to speed. And as writers in the series have had to work from home, like many people, they’re sharing their remote experiences in these newer episodes and answering questions from viewers.

In episode 12, writer Maxx Ramos guides you through working with Microsoft Edge, specifically on using Collections to organize the many, many tabs you may have open on your browser. This way, you can quickly pull up the tabs according to those collections, which could align to shopping, research or any project. She also shows you how to quickly pick up where you left off with your tabs.
Find out more about “Simply Windows” and check out a playlist of previous shows. Windows Community also has videos on the new Microsoft Edge and managing favorites, if you want to know more about that.
And if you like this, check out other Windows 10 Tips.

Now available: new State of Decay 2 Plunder Pack and Green Zone update | Windows Experience Blog

State of Decay 2 recently celebrated its two-year anniversary with new weapons, clothes, gameplay improvements and more. Now its fans can enjoy a new Plunder Pack and Green Zone updates.
The new Plunder Pack adds Sea of Thieves-themed weapons, outfits, hats and one seriously salty vehicle to the game. The Green Zone is a more relaxed, accessible apocalypse; where enemies do less damage, maintaining the community becomes easier due to cheaper crafting and more resources from scavenging and your Stamina lasts longer.
The update is available for all players, with State of Decay 2: Juggernaut Edition available with Xbox Game Pass, Xbox One, Windows 10 PC, Steam and the Epic Games Store. Get all the details over at Xbox Wire.

Announcing Windows 10 Insider Preview Build 19645 | Windows Experience Blog

Hello Windows Insiders, today we’re releasing Windows 10 Insider Preview Build 19645 to Windows Insiders in the Fast ring.
You can check out our Windows Insider Program documentation here, including a list of all the new features and updates released in builds so far. Not seeing any of the features in this build? Check your Windows Insider Settings to make sure you’re on the Fast ring. Submit feedback here to let us know if things weren’t working the way you expected.
If you want a complete look at what build is in which Insider ring, head over to Flight Hub. Please note, there will be a slight delay between when a build is flighted and when Flight Hub is updated.

Your Phone app’s audio controls feature now rolling out to the public
The audio controls functionality announced in April is now rolling out to the general public. This feature lets you control your music and audio apps from the Your Phone app. Now you can access and control the audio apps playing from your phone directly within the app, without needing to split your attention between devices or breaking your workflow. Your audio tracks will stay in sync between your phone and PC, and you can switch between multiple sources using the dropdown in the player.
Please make sure you have the latest versions of Your Phone Companion and the Your Phone app to experience this feature.

We changed the servicing model for the Linux kernel inside of Windows Subsystem for Linux 2 distributions. This build includes this change to remove the Linux kernel from the Windows image, and instead have it be serviced via Microsoft Update, the same way that 3rd party drivers (like graphics, or touchpad drivers) are installed and updated on your machine today. For full details please read this blog post on the Windows Command Line blog and for information about the kernel version please view the kernel docs page here.
Support for Nested Virtualization on AMD processors is now available. Being an early release we recommend you read this blog post for details on what platforms currently work as well as how to enable the feature.

We’ve fixed an issue where some devices booting from eMMC storage bugchecked when resuming from hibernate.
We fixed multiple Japanese and Chinese IME issues that impacted IME mode switching within applications and Windows notification area.
We’ve fixed an issue where taskbar preview thumbnails weren’t rendering consistently (showing a blank area).
We fixed an issue resulting in the handwriting input panel not appearing in certain text fields after being tapped with a pen.
We fixed an issue where resizing a snapped application in tablet mode would minimize the app to the taskbar instead of adjusting the app size.
We fixed an issue where Windows Hello Setup would crash if facial recognition was already set up and you chose the Improve Recognition button.
We fixed an issue for some users where your PC wouldn’t recognize it when you inserted a smart card (event log showing error 621).

We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
We’re working on fixing an issue for a future Insider Preview build where in Settings > Privacy, the Documents and Downloads sections show a broken icon next to their page name (just a rectangle).
Thanks,BLB

Announcing Windows 10 Insider Preview Build 19640 | Windows Experience Blog

Hello Windows Insiders, today we’re releasing Windows 10 Insider Preview Build 19640 to Windows Insiders in the Fast ring.
You can check out our Windows Insider Program documentation here, including a list of all the new features and updates released in builds so far. Not seeing any of the features in this build? Check your Windows Insider Settings to make sure you’re on the Fast ring. Submit feedback here to let us know if things weren’t working the way you expected.
If you want a complete look at what build is in which Insider ring, head over to Flight Hub. Please note, there will be a slight delay between when a build is flighted and when Flight Hub is updated.

Based on feedback, if your Downloads folder is synced to a cloud provider, we are disabling the option to have Storage Sense automatically clear out your Downloads folder on a cycle.
We updated our login logic, so if your PC is set up so you need to type in your username when logging in, accidentally starting your username with a space will no longer result in an error.

We’re looking into an issue where some devices booting from eMMC storage bugchecked when resuming from hibernate.
We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
We’re working on fixing an issue for a future Insider Preview build where in Settings > Privacy, the Documents and Downloads sections show a broken icon next to their page name (just a rectangle).
We’re looking into reports that taskbar preview thumbnails aren’t rendering consistently (showing a blank area).
Thanks,BLB