Windows 10 feature discussion: positives and negatives


Recommended Posts

MS Bob 10

I upgraded to Windows 10 because I found some features that were genuine improvements over Windows 7/8.1 but these are obscure features (WHPX or Windows Hypervisor Platform, Discrete Device Assignment for Hyper-V VMs, Hotspot with DHCP that works reliably with 5 GHz/choice of Wi-Fi band, Webcam frame server/webcam proxy, WDDM GPU scheduling). Also many platform/hardware features of my Intel/AMD CPUs or NVIDIA GPU supported only under 10. And of course continuously improving security.

And the backward steps in 10 related to UI, customizations, full control over the OS - mostly I managed to fix with third party apps with the exception of Modern Standby nonsense which is a hardware level regression due to firmware lacking S3 in my machines. There are some major annoying bugs in 10 for which I found workarounds - overall 7 was more fine-tuned, bug-free due to way it was built and patched vs 10's continuous major releases.

With Windows next-gen on the horizon, I'd really like to know why other people upgraded to 10. Overall, how do the releases from 1507 to 21H1 round up for you? Any killer features in any of the releases that you liked? Was it because you had no choice and 10 was the only supported version? What do you like in 10 that's not in 7/8.1? What do you find that's a technical or user experience improvement? What are the positives and negatives over more than 10 "versions" of Windows 10? How do you feel Windows 10 has rounded up being?

Tell me any features that you find particularly nice over 7/8.1. :) And what you don't like, apart from updates breaking something. That has been discussed to no end.

Link to post
Share on other sites

  • 4 weeks later...

I really like Windows Defender. It's not the best antivirus by any means but I like how it was integrated with the rest of the Windows 10 UI. I also like the new icons and just how modern it looks and feels.

Link to post
Share on other sites

Create an account or sign in to comment

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

Create an account

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

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Abhay V
      Microsoft releases optional Windows 10 updates with a ton of fixes
      by Abhay Venkatesh

      Microsoft has released cumulative updates for the three most recent versions of Windows 10, along with version 1909 currently supported for specific SKUs, as part of its “C” week release. These optional “quality” updates are usually released one or two weeks after Patch Tuesday. These fixes will also be rolled into the next month’s Patch Tuesday updates for those who choose to avoid installing these patches.

      The update rolling out to Windows 10 versions 2004, 20H2, and 21H1 is KB5004296, bumping up the build numbers to 19041.1151, 19042.1151, and 19043.1151, respectively. Since the three versions are based on the same codebase – with versions 20H2 and 21H1 being just enablement packages –, they are serviced with identical patches.

      The same update will soon roll out to Insiders running Windows 10 version 21H2 in the Release Preview channel, bumping the version to 19044.1151. These are Insiders that were moved from the Beta channel to Release Preview due to the incompatibility of their systems for Windows 11. Users with compatible devices, however, received the first Windows 11 build today.

      As for what’s new with the updates, there is the usual crop of bug fixes, addressing issues with gaming reliability and more. While the changelog does note a fix for a printing issue when using a USB connection, the firm is yet to address the problem relating to printing and scanning when using smart card authentication.

      Here are the highlights of the updates heading out to versions 2004, 20H2, and 21H1:

      And here is the complete list of fixes, which is a fairly long one:

      And here are the known issues listed in the changelog that users must be aware of:



      When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually.

      Note The affected apps are using the ImmGetCompositionString() function.

      We are working on a resolution and will provide an update in an upcoming release.

      Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later.

      Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps.

      To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the using SSU:

      Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu / Extract the SSU from the previously extracted cab via this command line: expand /f:* You will then have the SSU cab, in this example named Slipstream this file into your offline image first, then the LCU. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business

      After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING".

      For more information and a workaround, see KB5005322.

      Those running Windows 10 version 1909 Enterprise, Education, or IoT Enterprise will be offered KB5004293, bumping up the version to build 18363.1714. You can head to the knowledge base article to look at the complete list of fixes and known issues.

      Those looking to download the update manually can do so from the Update Catalog here for versions 2004, 20H2, and 21H1, and here for version 1909. However, the updated packages have not been made available at the time of writing. As mentioned earlier, these updates will show up as optional updates and are opt-in only. The fixes in these patches will be rolled into the Patch Tuesday packages next month.

    • By hellowalkman
      Google thinks bug hunting could get easier thanks to its new unified platform
      by Sayan Sen

      Google has launched today its new dedicated website for bug hunters which can be accessed via the following URL: The new website unifies all the Vulnerability Rewards Program (VRPs), which comprises Google, Android, Chrome, Google Play, as well as Abuse, and should make submitting newfound bug reports and such easier. The platform has been launched to celebrate the 10-year anniversary of the VRP launch although the celebration appears to be a bit late.

      Other improvements that Google notes are detailed below:

      Google says that when it launched its bug-hunting program back in 2010, the company received 25 reports far exceeding the expectations, and after 10 years, here's how it stands:

      Total bugs rewarded: 11,055

      Number of rewarded researchers: 2,022

      Total rewards: $29,357,516

      You may find more information on the official blog post here.

    • By Abhay V
      AdDuplex: Windows 10 version 21H1 is now on over 26% of PCs, Windows 11 makes its debut
      by Abhay Venkatesh

      After a gap of a couple of months, AdDuplex has released its Windows version usage report for the month of July. The report is collected from 5,000 Microsoft Store apps that are running the AdDuplex SDK v.2 or higher, and around 60,000 Windows PCs were sampled for this report. This month’s highlight is the debut of Windows 11, which was formally announced in June. As for Windows 10, version 21H1 that was released in May is now running on over 26% of Windows machines.

      Just like the October 2020 Update, the Windows 10 May 2021 Update was an enablement package that light up new features in the OS. The underlying codebase for 21H1, however, is identical to versions 20H2 and 2004, meaning that the three most recent versions are serviced with the same cumulative updates. It is, therefore, not surprising to see that the rollout of the latest version has been faster than the previous versions has seen. This is only expected to increase as version 2004 begins to reach the end of support for consumer SKUs.

      With Windows 10 21H1 now on more than 26% of PCs, the three latest versions of the OS account for close to 88% of usage share. The title for the most famous version of Windows 10 is retained by version 20H2 at 36.3%, followed by version 2004 at 24.6%. Windows Insiders running Windows 11 in the Dev channel account for close to 1% of total devices.

      Windows 10 version 21H2 is also slated to be an enablement package. However, with Windows 11 expected to begin rolling out later this year, it will be interesting to see how the usage share changes, since there are still questions about the pace of the rollout and what the final hardware specifications will be.

    • By Steven P.
      This Windows Hello webcam with privacy shutter is 20% off for only $67.99
      by Steven Parker

      Today on Amazon, you can pick up the wo-we Windows Hello Face Recognition Webcam for only $67.99 when you apply the $20 coupon, saving you 17% off the $84.99 list price.

      A nice thing about this webcam is not only is it a cheap way into Windows Hello password-less sign-in on Windows, but also has a manual privacy shutter, something you don't get on the more than doubly expensive Logi Brio webcam.

      Here are a few of its highlights:

      Below are a few of this camera's specifications, besides being compliant with Windows Hello.

      This item qualifies for free delivery, and the prices mentioned here are before taxes. It also includes standard manufacturer's warranty for which Amazon says you need to contact the seller.

      Get the wo-we Windows Hello Face Recognition Webcam for $67.99 (list price $84.99) 20% off

      As an Amazon Associate, Neowin may earn commission from qualifying purchases.

    • By hellowalkman
      Windows July update breaks printing and scanning when using smart-cards
      by Sayan Sen

      Microsoft seems to be having to deal with issues related to printers for a while now. This year alone, starting with the March update that caused the blue screen of death (BSOD) when trying to print, and more recently with the PrintNightmare print spooler service vulnerability. And Microsoft's troubles aren't stopping there.

      Today, the firm has confirmed that its recent July security update version KB5004237, which was released on July 13, is causing problems when printing on certain systems when trying to utilize smart cards for user authentication. This time, alongside printing problems, scanning on such systems may also not work.

      According to the Redmond firm, the KB5004237 July 13 cumulative update fixed printing problems on such printers that were connected via USB. However, it seems the update has also introduced a new bug as a result of the changes made for dealing with the CVE-2021-33764 vulnerability. This is causing the new issue on Domain Controller servers which act as gatekeepers responsible for dealing with such authentication requests.

      It has been noted however that while working with smart cards may fail, username and password authentication should work without issue. Here's how Microsoft has described the problem:

      The problem has been detailed a bit more under KB5005408 which explains that client printers and scanners must be compliant with either of the following:

      Here, KDC refers to a Key Distribution Center.

      The Windows platforms affected by this issue are:

      Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1

      Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

      Microsoft has said that it's investigating the issue and will provide a temporary workaround. For people having problems, the company has asked to update the necessary drivers and firmware and to consult with the device manufacturers when needed. You may find more details about the problem here on the company's official page.