Windows 10 20H2

To be honest I freaking hate that they are ditching the control panel. Hate the new settings panel.. Barely use it

 

November 10, 2020—KB4586781 (OS Builds 19041.630 and 19042.630) + KB4586864 as SSU

Known issues for KB4586781

• Microsoft Input Method Editor (IME) users for Japanese or Chinese may encounter problems performing various tasks. You may have trouble typing, get unexpected results, or you may not be able to enter text.
• You can see currently outstanding problems here .
• System and user certificates can be lost when a device is upgraded from Windows 10, version 1809 or later to a later version of Windows 10. Devices are only affected if they have already installed the latest cumulative update (LCU) that was released on September 16, 2020 or later, and then from media or an installation source that did not include an LCU dated October 13, 2020 or later , upgrade to a newer version of Windows 10. This primarily happens when managed devices with outdated bundles or media are updated using an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This can also happen when using outdated physical media or ISO images,Workaround see here
• It looks like the error 0x800f0988 also happens with this update for some . Don't have to, can. Packages for the update may be missing here so that it runs correctly. Ben made a fix for this that has been helping many since August.

Problems fixed by KB4586781

• Updates to improve security when using input devices such as a mouse, keyboard or pen.
• Updates to improve security when using Microsoft Office products.
• Updates to improve security when Windows performs basic operations.
• Updates the DST 2020 start date for the Fiji Islands to December 20, 2020.
• Security updates to Microsoft Scripting Engine, Windows Input and Composition, Microsoft Graphics, Windows Wallet Service, Windows Basics, and Windows Kernel.

Remember the servicing stack update must be installed first.

1) SSU (Servicing Stack Update) - KB4586864

2) CU (Cumulative Update) - KB4586781


November 10, 2020-KB4580419 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10, version 2004, Windows Server, version 2004, Windows 10, version 20H2, and Windows Server, version 20H2

DotnetCU:
http://download.windowsupdate.com/c..._197efbd77177abe76a587359cea77bda5398c594.msu


KB4589212, KB4589211 New microcode updates for Windows 10 20H2 up to 1507

In short: Microsoft has updated the microcode updates for Windows 10. It is KB4589212 for Windows 10 20H2 and 2004.

Windows 10 20H2 / 2004 support.microsoft.com/KB4589212 Update catalog: catalog.update.microsoft.com/KB4589212

Hate it? It's Disguting!

 

You know Papusan, just in the interest of performance mainly, is there a particularly recent windows update that is about the most optimal with say a Deskmodder patch? I thought about either rolling back or doing the patch, but I would just like to know an optimal update time with an optimal patch. Ask me about phone plans and can help you, but this I am kind of clueless on.

 

I haven't this Win version on my machines. I only installed it for benching/testing and uninstalled afterwards (on test machine). If you have problems as you mentioned in previous post... Then roll-back to the working one. See also https://www.computerworld.com/artic...s-time-to-pause-those-windows-10-updates.html

Which feature release to pick?
I’m still a bit wishy-washy about the 2004 release because of some issues with passwords reported by users and I’m certainly not yet comfortable recommending 20H2. I am fully comfortable with the 1909 release.

The patch I posted a few days before from Deskmodder is exactly the same patch I posted here today Main difference is the new from today is the official one.

 

i use a program that divides my hard drive in half and run a stable version of Win10 and run the latest fast ring release on the other half. I am also starting to experiment with linux and Qubes

I have been running the Fast ring for years now. I have had mostly positive experience but then again i remove all of the bloat using a program from GIT HUB https://github.com/10se1ucgo/DisableWinTracking/

 

Did a dirty upgrade from 1809 to 1909 since W10 v2009 reviews are bad.

 

build 20257

 

Same, a few weeks ago. Didn't notice any change in perfomance, and it was the reason why i held on 1809 for so long. Sometimes it's better not to listen to the internet, i guess.

 

One more annoying thing is that I've noticed that on some games it says you have to have a certain version of w10 to play, I think Gears 5 is an example. But is that really true, anyone tried? Does the game hard block you from playing?

 

Well I reverted back to the 2004 update, which I have had no issues with thus far. I will give 20H2 another go in a month or so.

 

Yes. Asphalt is another one for example. Games that depend on windows store, almost all of them need a minimum windows version to run

 

hit, nail, head. If you listen to the select few here you would still be using ms dos. The latest w10 update is fast and stable. I have been using it on all my devices day one. I have had zero issues on any. Even my 2007 acer 7720. Fast and smooth.

 

I just fired up my acer. I am typing this on it now. 20H2, 2007 era notebook, 4gb ddr2 ram, 120gb ssd, 750hdd. This thing still works fine for most things. Try that with even a macbook from 2012. No new OS updates, software starts to be phased out and more. To run Big Sur you need a device from 2013 at least. Six years newer than this noteobok. Windows 10 20H2 runs on this notebook just fine.

 

Even worse - once your Mac is EOL according to Apple, you can’t install newer apps based on newer but incompatible SDKs. My mother’s 2011 iMac has been on high Sierra for a while now. Got a warning message that this would be last year to install Turbo Tax.


Sent from my iPhone using Tapatalk Pro

 

I will never buy another mac computer. Unlike their mobile devices which have great support for OS/software updates, their pcs have terrible support. I am now looking for the new updates for this notebook now. i am going to replace the cpu with a higher model, it has a t5750 and I am going to install the t9500, add four more gigs of ram, a new higher res screen and a faster ssd. pop in a more modern wifi card and be good for another few years with it.

 

Just want to update, I thought I was on 20H2 on my acer when in fact, I was using 2004. Now, I am on 2oH2 and the machine is faster, smoother and overall, just better than on 2004. Opening apps, windows etc are snappier and faster. Just another machine running 20H2 with great results.

 

Looks like Microsoft don't trust the latest and greatest. Probably a good decision. Not everyday you see they can use their head

Microsoft Begins Force-Upgrading Windows 10 v1903 Devices (Surprisingly Not to 2020 Versions)

But with this move, the company is bypassing 2020's two feature updates, version 2004 and version 20H2, casting doubts on Microsoft's confidence in the two recent versions of the operating system. The company has been extremely slow with the rollout process, with many users still waiting for an update notification for the May 2020 Update (version 2004), let alone the latest October 2020 Update (version 20H2).

Cumulative updates - November 2020 answers.microsoft.com


Early patching reports for November askwoody.com | November 14th, 2020 at 10:57 Susan Bradley

I’m seeing reports in www.patchmanagement.org from some admins reporting bsod’s after applying November updates to 2004 Windows 10. The BSOD occurs after going into sleep mode

So far the models that have reported issues are:

HP Envy x360

1.hp probook 650 g4
2.hp elite x2 1012 g2
3.hp probook 650 g5
4.hp elitebook x360 1040 g6

I’m not seeing issues on my 2004’s and 20H2’s but if you are on 1909 on these models you may want to ensure you stay there for a bit as I’ve not seen issues reported on the 1909 platform only the 2004.

P.S. I’m not sure if it’s related to the Thunderbolt SSD bsod issue or not.

Windows 10 KB4586781 fails to install and causes other bugs windowslatest.com | Yesterday

Windows 10 KB4586781, which was released in the second week of November, appears to be a fairly stable release when compared to older updates but it’s also plagued with installation issues.

Microsoft’s latest cumulative update doesn’t just fail to address a bug that performs TRIM command on non-SSD drives—but once again introduces installation issues, and other minor gremlins.

Windows 10 in-place upgrade bug means you can no longer keep your files windowslatest.com - November 15, 2020

Windows 10 in-place upgrade also retains settings and your customization. In fact, several pre-installed apps and their data also remain unchanged.

Unfortunately, following the release of Windows 10’s October 2020 Update, it’s no longer possible to save your apps, settings and files when performing an in-place upgrade.

Reinstalling Windows 10 is an easy and most effective way to fix all kinds of problems with the operating system. Microsoft allows you to refresh your Windows 10 installation with the Media Creation Tool.

Note that the Media Creation Tool works as expected when you upgrade from Windows 10 version 2004, but if you install the October 2020 Update (20H2) via Windows Update (enablement package), you’ll be forced to choose the “Nothing” option during an in-place upgrade and lose your files.

Microsoft sources told us that the problem will be fixed in December 2020 Patch Tuesday updates.

The weekend is still young. We will see what may pop up tomorrow

 

And yet, my 2007 notebook hums along with no issues on 20H2. All these things are so blown out of proportion by a couple of whiny haters here.

 

OpenCL and OpenGL Compatibility Pack

 

I still have one of those asus eeepc netbooks from I don't even remember, 2008 maybe. Still has Win7 on it works fine for on the go web browsing, msoffice, watching movies, even light gaming if I wanted to lol. It's static though, no new software on it for a long time.

 

20h2 was indeed faster for UI, but other programs suffered, and in particular was the prevalence of sudden crashes and program instability.

 

Anyone find a way around this yet??

 

I have not seen this in any of my programs as of yet.

 

Try delete Microsoft Defender (make a custom OS) or try another antivirus software.

Microsoft admits Windows 10 multitasking feature broken by update windowslatest.com - Nov 20, 2020

Windows 10 October 2020 Update, which is just a service pack style upgrade, was released in October. This update is a minor release, but it comes with new features....


November 19, 2020—KB4594440 (OS Builds 19041.631 and 19042.631) Out-of-band

Highlights

• Updates an issue that might cause Kerberos authentication and ticket renewal issues that are related to the implementation of CVE-2020-17049.

Improvements and fixes

This non-security update includes quality improvements. Key changes include:

• This build includes all the improvements from Windows 10, version 2004.
• No additional issues were documented for this release.

• Addresses issues with Kerberos authentication related to the PerformTicketSignature registry subkey value in CVE-2020-17049, which was a part of the November 10, 2020 Windows update. The following issues might occur on writable and read-only domain controllers (DC):
  • Kerberos service tickets and ticket-granting tickets (TGT) might not renew for non-Windows Kerberos clients when PerformTicketSignature is set to 1 (the default).
  • Service for User (S4U) scenarios, such as scheduled tasks, clustering, and services for line-of-business applications, might fail for all clients when PerformTicketSignature is set to 0.
  • S4UProxy delegation fails during ticket referral in cross-domain scenarios if DCs in intermediate domains are inconsistently updated and PerformTicketSignature is set to 1.

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

CU (Cumulative Update)—KB4594440

 

in-place upgrade problem fixed in the upcoming and not yet publicized KB4586853 update for 20H2:
https://www.deskmodder.de/blog/2020...661-19041-661-korrigiert-das-inplace-problem/

 

Unfortunately, it is still 20H2. They need a patch to undo that, LOL.

 

Now changed to 19041.662


KB4586853 [manual download] Windows 10 20H2 / 2004 19042.662 / 19041.662 corrects the inplace problem [2nd update]

The beauty...

Today's Windows 10 20H2 Build 19042.662 (KB4586853) brings the following improvements:

• We updated Internet Explorer’s About dialog to use the standard modern dialog.
• We fixed an issue that causes Narrator to stop responding after you unlock a device if Narrator was in use before you locked the device.
• We fixed an issue that fails to display the local account groups in the localized language even after you deploy the language pack.
• We fixed an issue that prevents a user from finding certain Microsoft Xbox consoles on a Windows device.
• 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 with a certain COM API that causes a memory leak.
• We fixed an issue that fails to display the Microsoft Xbox Game Bar app controls on supported monitors. This issue occurs in certain Microsoft DirectX® 9.0 (DX9) games that are running with Variable Refresh Rate enabled on these monitors.
• We fixed an issue that prevents the touch keyboard from opening in Universal Windows Platform (UWP) apps when USB devices are connected.
• We fixed an issue with USB 3.0 hubs. A device connected to the hub might stop working when you set the device to hibernate or restart the device.
• We fixed an issue that crops the touch keyboard when you use a Remote Desktop Connection on a device that has a different screen resolution.
• We fixed an issue with excessive network traffic that occurs when you use the Open File dialog box in File Explorer and browse to a shared folder that has the Previous Version feature available.
• We fixed an issue that causes the ImmGetCompositionString() function to return the full-width Hiragana when using the Microsoft Input Method Editor (IME) for Japanese instead of returning the half-width Katakana.
• We fixed an issue that prevents Jump list items from functioning. This occurs when you create them using the Windows Runtime (WinRT) Windows.UI.StartScreen API for desktop applications that are packaged in the MSIX format.
• We fixed an issue that prevents applications from receiving the Shift and Ctrl keystroke events when the Bopomofo, Changjie, or Quick Input Method Editors (IME) are in use.
• We fixed an issue that randomly changes the input focus of edit controls when using the Japanese IME or the Chinese Traditional IME.
• We fixed an issue that prevents you from signing in on certain servers. This occurs when you enable a Group Policy that forces the start of a computer session to be interactive.
• We fixed an issue that fails to set the desktop wallpaper as configured by a GPO when you specify the local background as a solid color.
• We fixed an issue with the Microsoft Pinyin IME that unexpectedly dismisses the candidate pane when you type certain phrases.
• We fixed an issue that fails to send the Shift keyup event to an application when you use the Japanese IME.
• We fixed an issue that renders Kaomoji incorrectly on the emoji panel.
• We fixed an issue that makes the touch keyboard unstable in the Mail app.
• We fixed an issue that enters unexpected characters, such as half-width Hiragana, when you type a password while the IME is in Kana input mode.
• We fixed an issue that might fail to pair certain MIDI devices that connect using Bluetooth Low Energy (LE).
• We fixed a runtime error that causes Visual Basic 6.0 (VB6) to stop working when duplicate windows messages are sent to WindowProc().
• We fixed an issue that generates a 0x57 error when the wecutil ss /c: command is used to update an Event Forwarding subscription.
• We fixed an issue that causes applications to fail when they call the LookupAccountSid() API. This occurs after migrating accounts to a new domain whose name is shorter than the name of the previous domain.
• We fixed an issue in which loading a Code Integrity Policy causes PowerShell to leak a large amount of memory.
• We fixed an issue that causes a system to stop working during startup. This occurs when the CrashOnAuditFail policy is set to 1 and command-line argument auditing is turned on.
• We fixed an issue that causes the Microsoft Management Console (MMC) Group Policy application to stop working when you are editing the Group Policy Security settings. The error message is, “MMC cannot initialize the snap-in.”
• We fixed an issue that fails to free a system’s non-paged pool and requires a restart of the system. This occurs when running 32-bit applications with the Federal Information Processing Standard (FIPS) mode enabled.
• We fixed an issue that might prevent updates from installing and generates an “E_UNEXPECTED” error.
• We fixed an issue that causes the “I forgot my Pin” functionality on the lock screen to fail. This failure occurs if the user has signed in using a username and password and the DontDisplayLastUserName or HideFastUserSwitching policy settings are enabled.
• We fixed an issue that prevents access to Azure Active Directory (AD) using the Google Chrome browser because of a Conditional Access policy error.
• We improved the visual quality of Windows Mixed Reality headsets that run in lower resolution mode.
• We extended Microsoft Defender for Endpoint support to new regions.
• We enabled a new Hardware-enforced Stack Protection feature called shadow stacks on supported hardware. This update allows applications to opt in to user-mode shadow stack protection, which helps harden backward-edge control-flow integrity and prevents return-oriented programming-based attacks.
• We fixed an issue in the Microsoft Remote Procedure Call (RPC) runtime that causes the Distributed File System Replication (DFSR) service to stop responding. This issue generates log events for DFS Replication (5014), RPC (1726), and no reconnection (5004) for a default timeout of 24 hours with no replication.
• We added the touch keyboard to the allowed apps list, and it now works in multi-app assigned access mode.
• We fixed an issue that prevents the PDF24 app, version 9.1.1, from opening .txt files.
• We fixed an issue that might cause a non-paged pool memory leak in some scenarios.
• We fixed an issue that allows an app that has been blocked from hydrating files to continue hydrating files in some cases.
• We fixed an issue that might cause a memory leak in bindflt.sys when copying files in a container scenario.
• We fixed an issue with Active Directory Certificate Services (AD CS) that fails to submit Certificate Transparency (CT) logs when they are enabled.
• We fixed an issue in which cluster validation tests internal switches that are not for cluster use and re-communication.
• We fixed an issue that causes stop error 0x27 when you attempt to sign in to a device that is not in a domain using credentials for a device that is in the domain.
• We fixed an issue that causes a device to continually restart after installing an app.
• We fixed issues with Kerberos authentication related to the PerformTicketSignature registry subkey value in CVE-2020-17049, which was a part of the November 10, 2020 Windows update. The following issues might occur on writable and read-only domain controllers (DC):
  • Kerberos service tickets and ticket-granting tickets (TGT) might not renew for non-Windows Kerberos clients when PerformTicketSignature is set to 1 (the default).
  • Service for User (S4U) scenarios, such as scheduled tasks, clustering, and services for line-of-business applications, might fail for all clients when PerformTicketSignature is set to 0.
  • S4UProxy delegation fails during ticket referral in cross-domain scenarios if DCs in intermediate domains are inconsistently updated and PerformTicketSignature is set to 1.

For more details, head over to the official blog post.

I wonder why so many people still think the latest and greatest works as intended.



MICROSOFT
Windows 10 Defrag TRIM bug still not fixed after six months bleepingcomputeres.com

After the release of two Windows 10 feature updates and numerous cumulative updates, Microsoft has still not fixed a bug causing Windows Defrag to TRIM non-SSD drives.


Alt + Tab problem in Windows 10 20H2 19042.661 (KB4586853) fixed? deskmodder.com November 23, 2020 8:28

Since Windows 10 19042.487 there has been a problem with the key combination Alt + Tab. The wrong window opens. This error is also still included in Windows 10 20H2 19042.630. Microsoft itself has this problem in Insider 20231

So it may well be that Microsoft not only corrected the problem with the inplace repair in Windows 10 20H2, but also the Alt + Tab problem.


Microsoft admits Windows 10 multitasking feature broken by update windowslatest.com

Windows 10 October 2020 Update, which is just a service pack style upgrade, was released in October. This update is a minor release, but it comes with two new features --- theme-aware Start Menu...

 

The stupid sheeple always outnumber the smarter ones by a very large margin.

 

I added in all fixes and improvement on latest and greatest patch in my post above. A very disgusting list.

Latest news... Of course with Windows 10 October 2020 Update. I wonder why this version get so much love. Because it's flawed? Or because the older versions has become a bit more stable, hence less love?


Watch out for these new annoying bugs in Windows 10 windowslatest.com - November 24, 2020

Windows 10 October 2020 Update, also known as version 20H2, is a fairly stable release with nifty improvements but it's far from perfect and new bugs are now hitting some users after recent patches.

 

I am guessing you and the other hater in the "not Stupid" catagory? ha ha ha. funny guy! I love being called stupid every day...too fuuny, However, There is more than just me thinks both of you are beyond insane.

 

Using the "latest and greatest" rarely works well, especially in software.

Microsoft seems to be using people as free beta testers with Windows 10, I swear I've not had this many problems since Windows 98.

 

Just the opposite here. Windows 10 has been perfectly reliable for me. The issues I had were hardware related. Meaning, my SSHD craped out on me. So I had to re install. I have been on the latest version of 10 since it's been released. It's been perfect. Once people start messing with it using shut up this or that, trying to "make it faster", which never works, and tweaking crap for silly reasons, is when issues start. Load it and use it.

 

May want to re-check if W10 issued TRIM on a SSHD and may have killed earlier than expected? 20h1/2 had this issue.

 

It died long before 20h1/2 was release...like over two years ago. As I said, there are like 3-4 people here who have "issues" with windows. they are hacking it, "tweaking it", and gereally ruining it because they think its spying on them 24/7. so, lets say 6 people here, out of how many windows users here....It's not windows that is the problem.

 

Problem with the reading? http://forum.notebookreview.com/threads/windows-10-20h2.830339/page-48#post-11060516

In May 2020, Microsoft released Windows 10 2004, the May 2020 Update, and introduced two bugs causing SSD drives to be defragged too often and for the TRIM operation to be attempted on non-SSD drives.

 

Nope. Not at all. Do you? read what I said again....sorry HATER!

 

@kojack and @Papusan its good to keep people aware of your experience or sharing information like the positive and negative so keep us all updated to your findings. As for me, Im still on redstone 5 as I had bad experience before when updating to the latest and greatest. ^_^
Surprisingly I'm on Redstone 5 Home Edition and was able to update the LTSC version.. Saved me loads of time switching to LTSC doing a clean install..

 

Yeah, some of the problems I've encountered could be platform specific. But I'm always using older laptops, I'd expect W10 to have ironed out any issues.

The fact that Linux, which takes days for a proper configuration and can crap out because the bootloader didn't like something, is more stable than W10, just tells me that MS stopped caring about reliability and are now focused on "features"...

I don't even need any features from the host OS, it's there to run the hardware and let me run all the software that I actually use. I don't use any third party tweaking tools, they always tend to break something.

So far, I've had restarts for updates even though I explicitly set the update hours, blue screens that the recovery tools couldn't fix (full reinstall), partitions simply gone poof (easily recovered with testdisk), strange performance issues like Explorer taking up to several seconds to open, Search simply stopping working (not to mention Taskbar search is still dumber than W7), media sharing randomly stops working, and the coup the grace, laptop hibernating because of "CPU overheating" (it isn't). It happens randomly in the middle of work and drives me nuts.

This would be a golden opportunity for Linux... if it was a centrally managed OS without weird FOSS quirks like WINE developers being forbidden from reading/using Windows source code/files - wow, no wonder it's always behind.

 

I guess I am just "lucky". I have 2 acers, one s3 with an i5, 500 gb ssd and 4 gb of ram that my son uses. It's been on W10 since W10 came out and he has never had an issue. I have a 2007 7720 with 4gb ram a 120gb ssd and 750gb HDD and it's been running windows 10 since it's been released going through every update cycle without issue. My dell 13 5000 2 in 1 only had an issue because the SSHD crapped out, nothing to do with windows and has been on 10 since purchase and gone through every update cycle without issue. My wife's 11 3000 2 in1, which I am typing on now has been on windows 10 since new, with 4gb of ram and a 500gb ssd. It's gone through every update cycle without issue.

I have numerous desktops running in my two workshops behind my house both on w10 and going through every update cycle without issue. Like I said, from my experience windows 10 has been the most stable, easiest to use and visually appealing OS available. I have used Linux which is OK but not made for mainstream use, and I haveowned and used MacOS computers 3 different times (sucker for punishment) and that's just like using a computer from the early 90's. Remember how crappy that was? I do.

Again, most issues from windows 10 are from "experts" trying to tweak it to do things differently. Simple.

 

It's really strange, I had zero issues with Windows 7. Never seen a BSOD, even (except when undervolting, but that's understandable)! With the same software installed (OK, older versions, which might matter)...

 

Me either, the last time I can say I had any OS issues with windows was vista before service pack 2. ME was a nightmare.

 

Windows 7 is definitely the most stable and best-performing version of Windows that has ever been released. I had very few problems with any version of Windows prior to Windows 7 with the exception of ME. It was a piece of trash. And honestly, I haven't had many issues with Windoze 10 other than it is extremely bloated, slower (objective and measurable) and I personally find the UI to be unaesthetic and inefficient (subjective). Although, it is not nearly as ugly as 8.X was. Windows 10 also reflects the command and control, your data is our data, mindset that guides everything the Digi-Nazis do now, which I also find reprehensible.

 

Linux forum is right below this one. You would be better off there!

 

LOL. Maybe you should spend more time on Reddit, Facebook and Twitter. Or, actually read what people post rather than cherry-picking items to troll with.

 

Don't need to I get my news from trusted sources, and also from my on experiences. Not hearsay. Maybe you should give it a try sometime. Or, like I said, move on to linux. You know what the definition of insanity is right? Trying the same thing over and over expecting a different result. If you have such issue with windows 10, by all means, try the forum below this one. You may find it better than pissing and moaning about nonsense here.

Speaking of Trolling, maybe look in the mirror instead of constantly *****ing here.

 

Not cherry picked but the truth. They release new features and kill what some people want. I'm 100% sure they build their new OS around own Jokebooks. Always connected as smarthphones just means telemetry can call home back to mama 24/7/365.

Windows 10 V2004 and the 'Modern Standby' problem that cannot be switched off
Posted on November 26, 2020 by Günter Born

​

I may have a solution to a problem that does not exist - at least not for Microsoft. In the Windows 10 May 2020 update (version 2004) and in the successor 20H2, the previously optional function 'Connected Standby' has given way to 'Modern Standby'. This option can no longer be switched off, which can cause problems with various software.

In this article is an issue for a system that supports the S0 Modern standby is shown. A rant about the modern standby mode that can no longer be switched off in Windows 10 V2004 can be found in the Technet forum - people are pretty pissed off.

 

^^^ #492-495

 

Haters gonna hate. Well don't select modern standby until this issue is fixed. User error....not MS error.

 

I don't think you understand... See this nice post by @maffle "I was just tired of Dell and also Microsoft", both forcing you into Modern Standby, which never worked, doesnt work, and will not ever work reliable....

Fail | Microsoft Modern Standby is causing some XPS, Lenovo and Asus laptops to heat up like crazy
It's not comforting when the laptop in your backpack or bag would heat up to over 50 C or 120 F seemingly out of nowhere. Microsoft's latest feature can be undesirable in most cases especially to users who are unaware of the differences between Modern Standby and traditional S3 sleep

And isn't it amusing? Dell have made place an own section for Modern standby on their Dell community tech forum. Maybe @maffle @Dennismungai @abujafar can teach yoo.



Windows 10: Do not save energy, just balanced in the settings - the modern standby is "to blame" deskmodder.de

This is not a bug, but is due to the "modern standby" (connected standby). Today we had this problem in our forum and Sassicaia was able to solve it. After executing the powercfg / a command in the command prompt , it was clear that only Standby S0 was activated on the system.

Since every manufacturer designs their bios differently, here is the general way as a solution:

1. Go to the Boot tab in the bios
2. There should be under the entry OS or similar, the choice between Windows 10 (WHQL) and "Other OS" (other OS). This setting is actually intended when you want to install Linux, for example. If you use the latter setting, then after activation and saving under powercfg / a , S3 is displayed again as Available.

Yeah, at least you was able to call it an issue

 

Alright, time to chill. Take a few hours away from these debates -- as urgent and important as they may seem -- and attend to family or friends. If you wonder whether I am referring to you, then yes, I am