Jump to content

Search the Community

Showing results for tags 'beta channel'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Categories

  • Drivers
  • Filesharing
    • BitTorrent
    • eDonkey & Direct Connect (DC)
    • NewsReaders (Usenet)
    • Other P2P Clients & Tools
  • Internet
    • Download Managers & FTP Clients
    • Messengers
    • Web Browsers
    • Other Internet Tools
  • Multimedia
    • Codecs & Converters
    • Image Viewers & Editors
    • Media Players
    • Other Multimedia Software
  • Security
    • Anti-Malware
    • Firewalls
    • Other Security Tools
  • System
    • Benchmarking & System Info
    • Customization
    • Defrag Tools
    • Disc & Registry Cleaners
    • Management Suites
    • Other System Tools
  • Other Apps
    • Burning & Imaging
    • Document Viewers & Editors
    • File Managers & Archivers
    • Miscellaneous Applications
  • Linux Distributions

Categories

  • General News
  • File Sharing News
  • Mobile News
  • Software News
  • Security & Privacy News
  • Technology News

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 9 results

  1. Microsoft Edge 92 rolls out to the Beta channel with vertical tabs improvements and more Microsoft has begun rolling out Edge version 92 to users in the Beta channel, sticking to the timeline mentioned in the release schedule. As is the case generally, there is no official changelog yet as the firm usually posts it later in the day. However, the version has been in testing in the Canary and Dev channels for a while now, so there is a fair bit of information on what is new. When the changelog does get posted, it can be found here. With version 92 being promoted to the Beta channel, both Dev and Beta channels users are now running the same major version. However, that is expected to change soon as the company is slated to release the first Edge 93 build to Dev channel testers this week. The firm does note on the first-load welcome page for the Beta update that there isn’t much to talk about with this latest release. However, the Redmond giant is detailing the various announcements from the past few weeks, including those made during its Build conference. As for what’s new in version 92, there are improvements to vertical tabs, with the browser now letting users turn the feature off across all open windows. Users can also choose to hide the title bar when vertical tabs are enabled. Edge 92 also introduces automatic HTTPS that switches connections to the secure protocol on sites that support it. The firm is also bringing new font rendering improvements to improve rendering at higher contrast levels. The feature is currently hidden behind a flag. Other minor improvements include enhancements to pinning History and Downloads menus, Immersive Reader additions, and improvements to PWA menus that are installed as apps on the desktop. Those interested in reading through the changelogs for the complete list of Dev channel releases for version 92 can navigate to the individual posts below: Edge Dev 92.0.873.1 Edge Dev 92.0.878.0 Edge Dev 92.0.884.2 Edge Dev 92.0.891.1 Edge Dev 92.0.902.2 Considering that the update has just begun rolling out, it might be a while before it shows up for all Beta channel users. You can also force check for an update by heading into Settings > Help and feedback > About Microsoft Edge. As usual, the release will eventually make it to all users and install in the background. Microsoft Edge 92 rolls out to the Beta channel with vertical tabs improvements and more
  2. Microsoft releases new Office Build 13801.20004(Beta Channel) for Windows users Microsoft today released a new Office Insider Preview Build 13801.20004 for Windows users registered in the Beta Channel. The new Insider Preview build brings a new feature for Access, and bug fixes for issues found in Excel, Outlook, PowerPoint, Word. You can read the full official changelog below. Changelog Access New feature You will now see selected tabs clearer in Access. Excel Notable fixes We fixed an issue where Excel would stop responding after selecting a data series in a chart. We fixed an issue where pressing Enter with certain keyboards on Android would add a new line rather than moving to the next cell. We fixed an issue related to pictures retaining their aspect ratio during a crop operation. Outlook Notable fixes We fixed an issue that caused mails to be sent as digitally signed after the user unchecked that option. PowerPoint Notable fixes We fixed an issue related to pictures retaining their aspect ratio during a crop operation. Word Notable fixes We fixed an issue related to pictures retaining their aspect ratio during a crop operation. We fixed an issue which the comment may be truncated with links. We fixed an issue with conflict mode when coauthoring. We fixed an issue in saving to SharePoint Online We fixed an issue in exporting Word document to PDF. Office Suite Notable fixes We fixed an issue where Office would in some circumstances present sensitivity labels for one signed-in account when it should present sensitivity labels for a different signed-in account. To update to the latest Microsoft Office Insider Preview Build, open any Office program and go to File> Account> Update Options> Update Now. Microsoft releases new Office Build 13801.20004(Beta Channel) for Windows users
  3. Microsoft Edge 89 is out in the Beta channel, letting you reset your sync data Today, Microsoft is releasing a new build of Microsoft Edge to the Beta channel, which gets new builds every six weeks or so. This one is build 89.0.774.18, so this is the first Edge 89 build in the channel; there will be minor fixes in-between now and when it's released to the Stable channel. As always, there are a bunch of new features. For one thing, you can now reset your Edge sync data in the cloud. So, if you've had any issues with settings syncing in Edge that you just can't seem to fix, you can finally blow all of your settings away and start fresh. Another big one is that you can block auto-playing video, something that is universally hated by internet users. Now, you won't have to worry about going to a site and some advertisement starts yelling at you. There's also new lockdown capabilities for kiosk mode, which is meant to be more secure, obviously. There's a new Enterprise Mode Site List Manager tool,. which is available at edge://compat. You can create, edit, and export your site list for IE mode with that. As always, there are PDF improvements. Text selection is supposed to be smoother and more consistent. In the productivity department, date of birth fields are now supported in autofill, something that apparently didn't work before. Autofill suggestions can now include content from the clipboard, which should make it more seamless to paste content. Edge 89 is rolling out to the Beta channel now, and you can get it by going to Settings -> About Microsoft Edge. If you don't do that, it will update at some point in the background. Source: Microsoft Edge 89 is out in the Beta channel, letting you reset your sync data
  4. Microsoft releases Windows 10 Build 19042.508 (20H2) to Insiders in the Beta Channel Microsoft today announced the release of Windows 10 20H2 Build 19042.508 (KB4571756) to Windows Insiders in the Beta Channel. The build is intended for commercial customers in the Beta Channel and Release Preview Channel for pre-release validation. Windows 10 Build 19042.508 is a security update which includes the following improvements: Microsoft fixed an issue with a possible elevation of privilege in windowmanagement.dll. Microsoft fixed a security vulnerability issue with user proxies and HTTP-based intranet servers. After installing this update, HTTP-based intranet servers cannot leverage a user proxy by default to detect updates. Scans using these servers will fail if the clients do not have a configured system proxy. If you must leverage a user proxy, you must configure the behaviour using the Windows Update policy “Allow user proxy to be used as a fallback if detection using system proxy fails.” This change does not affect customers who secure their Windows Server Update Services (WSUS) servers with the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) protocols. For more information, see Improving security for devices receiving updates via WSUS. Security updates to Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Input and Composition, Windows Media, Windows Shell, Windows Cloud Infrastructure, Windows Fundamentals, Windows Management, Windows Kernel, Windows Virtualization, Windows Storage and Filesystems, and the Microsoft JET Database Engine. For more information about the resolved security vulnerabilities, see more at the Security Update Guide here. Insiders in the Beta channel can download the update by Checking for Updates in Settings. Source: Microsoft Microsoft releases Windows 10 Build 19042.508 (20H2) to Insiders in the Beta Channel
  5. Microsoft releases Windows 10 20H2 build 19042.450 to the Beta Channel As is customary on every second Tuesday of the month, Microsoft has released cumulative updates for all supported versions of Windows. This includes all supported Windows 10 versions, Windows 8.1 and respective Windows Server versions, and Windows 7 customers that have opted for Extended Security Updates (ESUs). Additionally, the firm is also releasing 20H2 build 19042.450 to Windows Insiders in the Beta Channel. While the updates to 20H2 builds in the Beta Channel – which is just a single build increment over the 20H1 builds – are cumulative updates that match the production version’s decimals, Microsoft served a ton of new features with build 19042.421, bringing the new theme aware Start Menu and Alt-Tab functionality between browser tabs. Interestingly, considering that the 20H2 builds are just extensions of the production versions released in the spring, and are served the same cumulative updates, those start menu themes are also hidden in the production version of Windows 10. Today’s 20H2 build brings a couple of security updates are resemble the fixes for version 2004, since it receives the exaction KB update (KB4566782) as the production build. Here is the list of fixes in this release: Addresses an issue in Universal Windows Platform (UWP) apps that allows single sign-on authentication when an app does not have the Enterprise Authentication capability. With the release of CVE-2020-1509, UWP applications might begin prompting the user for credentials. Security updates to the Microsoft Scripting Engine, Internet Explorer, Windows Graphics, Microsoft Graphics Component, Windows Kernel, Windows Input and Composition, Windows Media, Windows Shell, the Windows Wallet Service, Microsoft Edge Legacy, Windows Cloud Infrastructure, Windows Authentication, the Windows AI Platform, Windows Fundamentals, Windows Storage and Filesystems, Windows Update Stack, Windows File Server and Clustering, Windows Hybrid Storage Services, Windows App Platform and Frameworks, Microsoft JET Database Engine, and Windows SQL components. When version 20H2 is released to the public, an enablement package will bump up the build by one digit. As usual, today’s updates should begin downloading automatically via Windows Updates for Windows Insiders in the Beta Channel. Microsoft releases Windows 10 20H2 build 19042.450 to the Beta Channel
  6. Windows 10 20H2 build 19042.487 now out in the Beta Channel with a ton of fixes In addition to releasing Windows 10 vNext build 20201 today to the Dev channel, Microsoft is also releasing 20H2 build 19042.487 to the Beta Channel. The firm also reminded enterprise customers that it is making 20H2 available to commercial devices for pre-release testing in the Beta and Release Preview Channels, something that the firm announced last week. Today’s build, unsurprisingly, brings a bunch of fixes and quality improvements. There are no new major features. Windows 10 version 20H2, which is how the company now names releases, is a minor enablement package that will be rolled out to Windows 10 version 2004 (20H1) users sometime later this year. Both the versions share the same core, with some features that will be enabled in 20H2 already hidden in the May 2020 Update. The release for commercial testing also signals that the version is almost ready for prime time. Here is the list of fixes for this this build: We fixed an issue with pinned Add-ins that cause Microsoft Outlook to become unresponsive. We now provide the ability to sync the Microsoft Edge IE Mode unidirectional session cookie when an administrator configures the session cookie. We fixed an issue with rendering PeerDist-encoded content in Internet Explorer and Microsoft Edge. We fixed an issue that might prevent ActiveX content from loading. We fixed an issue that displays a black screen to Windows Virtual Desktop (WVD) users when they attempt to sign in. We fixed an issue that might cause apps that use the custom text wrapping function to stop working in certain scenarios. We fixed an issue with Start menu apps and tiles in virtual desktop infrastructure (VDI) environments. The issue occurs after you sign in to the VDI environment a second time and use a Remote Desktop User Profile Disk in a non-persistent virtual desktop pool. We fixed an issue that generates an error when printing to a document repository. We fixed an issue that prevents Visual Basic 6.0 (VB6) applications from using ListView in OCXafter upgrading to Windows 10, version 1903 and later. We fixed a runtime error that causes VB6 to stop working when duplicate windows messages are sent to WindowProc(). We fixed an issue that causes a stop error when the initialization of the graphics adapter fails. We fixed an issue to reduce the likelihood of missing fonts. We fixed an issue that prevents users from reducing the size of a window in some cases. We fixed an issue that causes the touch keyboard to close when you touch any key. We fixed an issue that adds an unwanted keyboard layout as the default after an upgrade or migration even if you have already removed the layout. We fixed an issue the prevents applications from closing even though programming code directs them to close. We fixed an issue that causes attempts to take a screenshot of a window using the PrintWindow API to fail. We fixed an issue with a memory leak in exe that occurs when you refresh an application that has an editable box. We fixed an issue that truncates a potential list of characters (candidates) when you type characters in the Simplified Chinese (Pinyin) input method editor (IME). When this happens, Chinese characters do not appear. We fixed an issue that prevents the first key stroke from being recognized correctly in the DataGridView We fixed an issue that causes an application that uses dll to stop working, and the 0xc0000005 (Access violation) exception appears. We fixed an issue with Dynamic Data Exchange (DDE) that causes a memory leak when multiple clients connect to the same server. We fixed an issue that prevents Cortana Smart lighting from working as expected if you shut down the machine while Fast Shutdown is enabled. We now provide the ability for Dolby Atmos for Headphones and DTS Headphone: X to be used in 24-bit mode on devices that support 24-bit audio. We fixed an issue that prevents the IME user dictionary from being used when leveraging folder redirection with user profiles. We fixed an issue that causes Microsoft Office applications to close unexpectedly when using a Korean IME. We fixed an issue that displays incorrect folder properties in File Explorer when the path is longer than MAX_PATH. We fixed an issue with a blurry sign in screen. We fixed an issue with Windows Update becoming unresponsive when checking for updates. We fixed an issue that prevents the correct lock screen from appearing when the following policies are set: Policy “Interactive Logon: Do not require Ctrl+Alt+Del” set to “Disabled” HKLM\SOFRWARE\Policies\Microsoft\Windows\System DisableLockScreenAppNotifications = 1 DisableLogonBackgroundImage = 1 We fixed an issue that causes File Explorer to stop working when you browse directories of raw images and other file types. We have improved the tablet experience for convertible or hybrid devices in docked scenarios. We have improved the user experience of the Windows Hello enrollment pages for face and fingerprint setup. We prevent accounts from a different tenant from signing in to a Surface Hub device. We have updated the time zone information for the Yukon, Canada. We fixed a stop error 0xC2 in sys. We have fixed an issue that causes the Event Viewer Microsoft Management Console (MMC) to stop working when the secondary monitor is above the primary monitor. An out of bounds exception appears. We have fixed an issue that prevents the migration of the Windows Remote Management (WinRM) service startup type. We have fixed an issue with object performance counters. We have fixed an issue that prevents Microsoft User Experience Virtualization (UE-V) settings from roaming to enable the signature files that are used for new messages, forwarded messages, and replies. We have fixed an issue that prevents users from setting the REG_EXPAND_SZkeys in some automated scenarios. We have fixed an issue with the EnhancedAppLayerSecurity node in modern device management (MDM) that prevents its setting from being applied correctly to client devices. We have fixed an issue that causes a memory leak in the exeprocess when the server is under a heavy authentication load and Credential Guard is enabled. We have fixed an issue that might cause a delay of up to two minutes when signing in or unlocking a session on Hybrid Azure Active Directory-joined machines. We have fixed an issue that prevents hash signing from working correctly when using the Microsoft Platform Crypto Provider for Trusted Platform Modules (TPM). This issue might also affect networking software, such as virtual private network (VPN) applications. We have fixed an issue that continues to display the previous username hint in the smart card sign in box after a different user has used the machine with domain credentials. We have fixed an issue that causes communication with the TPM to time out and fail. We have fixed an issue that sometimes prevents AppLocker from running an application whose publisher rule allows it to run. We have fixed an issue in which AppLocker publisher rules might sometimes prevent applications from loading software modules; this can cause partial application failure. We have fixed an issue that causes the promotion of a server to a domain controller to fail. This occurs when the Local Security Authority Subsystem Service (LSASS) process is set as Protected Process Light (PPL). We have fixed an issue that prevents you from unlocking a device if you typed a space before the username when you first signed in to the device. We have fixed an issue that causes a system to stop working and generates a 7E stop code. We have fixed an issue that causes applications to take a long time to open. We have fixed classification failures caused by the wrong User Principal Name (UPN). We have fixed an issue in cluster scenarios that causes handles to .vmcx and .vmrs files to become invalid after storage failover. As a result, live migration and other virtual machine (VM) maintenance activities fail with STATUS_UNEXPECTED_NETWORK_ERROR. We have fixed an issue with interrupt targeting that might cause an interrupt to arrive at an incorrect processor. We have fixed an issue that causes delays during shutdown when running the Microsoft Keyboard Filter Service. We have fixed an issue that causes a machine to request a new IP address after authentication. We fixed an issue that causes the Background Intelligent Transfer Service (BITS) to download data while a device is in cellular mode without explicit user permission. We fixed an issue that prevents Always On VPN (AOVPN) from automatically reconnecting when resuming from Sleep or Hibernate. We fixed an issue that causes AOVPN user tunnels to use an incorrect certificate. We fixed an issue with AOVPN that occurs when user and device tunnels are configured to connect to the same endpoint. We fixed an issue that causes VPN apps to stop working in some cases when they attempt to enumerate VPN profiles. We fixed an issue that causes the Optimize Drives dialog to incorrectly report that previously optimized drives need to be optimized again. We fixed an issue that fails to turn off the host memory buffer (HMB) when you force the shutdown of a device. As a result, solid-state drives (SSDs) do not delete HMB contents. We fixed an issue that prevents apps from downloading an update or opening in certain scenarios. We fixed an issue that might cause a stop error (0xC00002E3) at startup. This issue occurs after installing certain Windows Updates that were released on or after April 21, 2020. We fixed an issue that might cause stop error 7E in syson servers running the Network File System (NFS) service. We fixed an issue with Server Message Block (SMB). This issue incorrectly logs the Microsoft-Windows-SMBClient 31013 event in the Microsoft-Windows-SMBClient/Security event log of an SMB client when an SMB server returns STATUS_USER_SESSION_DELETED. This issue occurs when SMB client users or applications open multiple SMB sessions using the same set of Transmission Control Protocol (TCP) connections on the same SMB Server. This issue most likely occurs on Remote Desktop Servers. We fixed an issue that causes SMB to incorrectly use the original, cached non-Continuous Available handle to a file. This handle becomes invalid after a network error or storage failover. As a result, applications fail with errors such as STATUS_UNEXPECTED_NETWORK_ERROR. We fixed an issue that causes the loss of written data when an application opens a file and writes to the end of the file in a share folder. We fixed an issue with some apps, such as Microsoft Excel, that occurs when using the Microsoft Input Method Editor (IME) for Chinese and Japanese languages. You might receive an error, or the app might stop responding or close when you attempt to drag using the mouse. Considering that 20H2 and version 2004 are the same versions of Windows 10, these fixes should also be made available to the latter. Since these are not security updates, the fixes might also be released as an optional update soon and then be rolled into next month's Patch Tuesday updates. With the release now heading to commercial users as well, the Redmond firm has also made availabe 20H2 ISOs for users to download and perform a clean install. The company did mention in the blog post for commercial customers that the ISOs will be available soon from the Insider Preview Downloads page. Windows 10 20H2 build 19042.487 now out in the Beta Channel with a ton of fixes
  7. Today is Patch Tuesday, and that means that it's time for all supported versions of Windows to get updated. In the world of Windows 10, that still means every version except for version 1511, although different versions are only supported on certain SKUs. Windows 10 is a Microsoft product, so don't be surprised that support lifecycles ended up being much more complicated than originally intended. Ever since March, Patch Tuesday has been the only time that Windows 10 was getting updated. Microsoft paused optional updates because of the COVID-19 pandemic; however, things will be back to normal this month. If you're on the latest version of Windows 10, version 2004, then you'll get KB4565503, bringing the build number to 19041.388. You can manually download it here, and these are the highlights: Here's the full list of fixes: There's also one known issue that's caused by this cumulative update specifically, as opposed to the many known issues in Windows 10 version 2004 as a whole. Symptom Workaround When using some apps, such as Microsoft Excel, users of the Microsoft Input Method Editor (IME) for Chinese and Japanese might receive an error, or the app might stop responding or close when attempting to drag using the mouse. For more information and workaround steps, please see KB4564002. If you're on Windows 10 version 1909 or 1903, you'll be getting KB4565483, bringing the build number to 16363.959 or 18362.959, respectively. You can manually download it here, and these are the highlights: Here's the full list of fixes: This one also has one known issue: Symptom Workaround After installing this update on a Windows 10 device with a wireless wide area network (WWAN) LTE modem, reaching the internet might not be possible. However, the Network Connectivity Status Indicator (NCSI) in the notification area might still indicate that you are connected to the internet. We are working on a resolution and will provide an update in an upcoming release. If you're on Windows 10 version 1809, Microsoft will be moving you to version 2004 soon since 1809 is nearing the end of support. For now, you'll get KB4558998, bringing the build number to 17763.1339. You can manually download it here, and these are the highlights: Here's the full list of fixes: This one also has one known issue: Symptom Workaround After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_ COMPONENT_NOT_FOUND." Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release. Those are the updates that are supported for all versions of Windows 10. These are the rest, which are supported under various conditions: Version KB Build Download Support 1803 KB4565489 17134.1610 Update Catalog Enterprise and Education SKUs 1709 KB4565508 16299.1992 Update Catalog 1703 KB4565499 15063.2439 Update Catalog Surface Hub only 1607 KB4565511 14393.3808 Update Catalog Long-Term Servicing Branch 1507 KB4565513 10240.18638 Update Catalog As usual, you can install all of these manually, via Windows Update, or they'll be installed automatically at some point. Source: Microsoft releases Windows 10 build 19041.388, 18363.959 - here's what's new (via Neowin)
  8. Microsoft releases Windows 10 build 19042.421 with a ton of new features Today, Microsoft released Windows 10 Insider Preview build 19042.421 to the Beta channel. Unlike most cumulative updates for the Beta channel, this one actually contains a bunch of new features. In fact, many expected that 20H2 wouldn't have many new features at all, since it's going to be delivered in a similar way that 19H2 was delivered. One key new feature is the new tiles in the Start Menu, which debuted in the Dev channel. They're meant to be theme-aware, and they should all show a more uniform color. Another new feature is the ability to Alt+Tab between not only your open apps, but your tabs in Microsoft's Edge browser. There's that, and there's actually a bunch more. Here's the full list of changes: 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. ALT + TAB between apps and sites Are you a multitasker? With this build, your 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 requires a Canary or Dev build of Microsoft Edge (version 83.0.475.0 or higher). Improving pinned sites in Microsoft Edge We have another new feature we’ve been working on to make you more efficient when browsing the web: quick access to tabs for your pinned sites. Clicking a pinned site on the Taskbar will now show you all of the open tabs for that site across any of your Microsoft Edge windows, just like you’d expect for any app with multiple open windows. This feature requires Microsoft Edge Insider Build 85.0.561.0 or higher (Canary or Dev Channel). NOTE: Since this is an early preview, existing sites on your Taskbar will not experience this new behavior until you remove and re-pin them. 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. Modern Device Management (MDM) improvements The new Local Users and Groups modern device management (MDM) policy allows an administrator to make granular changes to a local group on a managed device, on par with what has been available to devices managed with on-prem Group Policy (GP). This is quite the list of features, and it's probably going to be all that we end up seeing in 20H2. After all, up until today, many would have thought that the only front-facing feature in 20H2 would be that it will ship with the new Edge browser. As always, you can install this new build through Settings. If you're not on the Beta channel yet, you can enroll through the Windows Insider Program tab in Settings. Microsoft releases Windows 10 build 19042.421 with a ton of new features
  9. It was almost a year ago that Microsoft announced that it's rebuilding its Edge browser from Google's open-source Chromium project. Today at its Ignite 2019 conference in Orlando, it finally announced that general availability is slated for January 15, and the release candidate is coming today. Well now, that release candidate is finally available from the Beta channel. The version number is 79.0.309.11; Dev and Canary are on the newer Chromium 80, which is to be expected given that they're updated more frequently. In fact, you can expect Edge Beta to move to Chromium 80 right before Edge 79 is released to production. Another announcement that was made recently was that Edge is getting a new logo, as you can see from the image above. Interestingly enough, this release candidate does not have the new icon, although we should be seeing it in builds later on this week, probably alongside new Canary and Dev builds that have it. But if you want to check out the release candidate now, you can download it here. Source: Microsoft's Edge Chromium release candidate is now available in the Beta channel (via Neowin)
×
×
  • Create New...