Windows 10: Microsoft acknowledges a new issue in several Windows 10 versions

Last week, we reported that Windows 10’s sfc /scannow command no longer works after the latest updates. The bug is hitting all supported versions of Windows 10 and the scannow command displays a generic error message, and the culprit appears to be the latest version of Windows Defender.

The sfc /scannow is a command to run System File Checker and repair Windows System files. Sfc /scannow (System File Checker) inspects important Windows files on the computer and replaces the corrupted file with a cached version.

After the latest updates, if you initiate a scan in any supported version of Windows 10 with the Windows System File Checker (sfc /scannow cmd command), the process would fail with the following error:

Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.



Checking the CBS log file reveals that the problem is linked to Windows Defender PowerShell Module. The log file also states error message “Hashes for file member do not match.”

Today, Microsoft has acknowledged this problem in a new support document. In the support document, Microsoft stated that sfc /scannow feature is not broken and there is a bug that causes System File Checker (SFC) to incorrectly flag Windows Defender PowerShell module files as corrupt.



Microsoft says the bug affects almost all versions of Windows 10, including the May 2019 Update and Windows 10 version 1607.

“This is a known issue in Windows 10 version 1607 and later versions, and Windows Defender version 4.18.1906.3 and later versions,” the company stated in the support document.

Microsoft has posted the following technical explanation:

The files for the Windows Defender PowerShell module that are located in %windir%\System32\WindowsPowerShell\v1.0\Modules\Defender ship as part of the Windows image. These files are catalog-signed. However, the manageability component of Windows Defender has a new out-of-band update channel. This channel replaces the original files with updated versions that are signed by using a Microsoft certificate that the Windows operating system trusts. Because of this change, SFC flags the updated files as “Hashes for file member do not match.”

Microsoft says it is working on a fix and SFC will stop flagging the files incorrectly in a new future version of Windows.

Users are advised to ignore the SFC error messages as the files are incorrectly marked as corrupt.

The post Microsoft acknowledges a new issue in several Windows 10 versions appeared first on Windows Latest

Weiterlesen...

 

Microsoft Acknowledges Gaming Performance Issues Under Win 10 Creators Update

Microsoft made considerable noise on their vaulted Game Mode, a Windows feature which made its appearance in their latest Creators Update version of Windows 10. Game Mode was one of the foremost features in the latest Windows update, which was supposed to deliver improved performance in gaming or other full-screen 3D applications, by enabling more of the available CPU and GPU resources to be tapped into by specific applications. Specific CPU (through winding down of non-crucial processes) and GPU (through prioritization of game-related graphics memory allocation) improvements were baked into this latest version; supposedly, only performance improvements should result from this effort on Microsoft's part.









However, things are not as rosy as they should be, and users soon started reporting performance issues with stuttering and lower than expected frame-rates under the latest version of Windows - which didn't occur prior to the Creators Update. Microsoft has been mum on the issue; until now. The company has now officially acknowledged that there are indeed situations where gamers could experience frame-rate and stuttering issues, and has even issued a fix for one such situation with the latest, fast-ring build 16273 and above versions of Windows. However, this has fixed only one of multiple origin points for the reported issues.

Some users are reporting that disabling the Xbox Game DVR feature eliminates the issues, but this isn't working for every user that remains affected. Likely, the issue lies with Microsoft's Game Mode interface and Xbox interface additions to Windows 10 with the Creators Update. It's somewhat of a paradox: at the same time that Microsoft introduces specific CPU and GPU workload optimizations for full-screen applications, they introduce an additional interface layer on top of your 3D application, enabling additional Xbox-based functionality (such as the aforementioned DVR capability). Likely, that's the culprit of the whole performance issues; it remains to be seen whether all sources of the performance issues will be fixed through windows updates, or if users will have to wait until the Fall Creators Update for a fully resolved scenario.





Sources: MS PowerUser, Windows Feedback Hub, via Neowin

 

New install Windows 10 (issue solved)

It's good that you're not experiencing any issues. Unfortunately many folks are, a quick Google search will show the same info im offering the OP.

Heres a couple examples:

Here

Here

It's basically what I mentioned above, small issues here and there ,but nothing to end your day.. for the most part.

I know it's anecdotal, but for my experience 95% of the time it's perfectly fine. The issues I've run into wouldn't be enough for me to roll back , but they would be enough (had I not installed it yet) ,to avoid it for another couple weeks which is why I'm suggesting it to the OP

Windows 10 Fall Creators Update problems and complaints

• Installation problems with the Fall Creators Update
• Microsoft Edge problems with the Fall Creators Update
• Drivers problems with the Fall Creators Update
• Experience problems with the Fall Creators Update

keep in mind, as of recently, the FCU is installed on 5% of devices roughly.....

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.