The June 2020 cumulative replace for Windows 10 launched by Microsoft has been inflicting printing points and different bugs for some customers. Now, customers report that they’re getting the error message “Windows cannot find [*.exe]” once they launch apps resembling Microsoft Office.
This has been reported by customers on Microsoft’s discussion board and the bug is reportedly brought on by Windows 10 KB4560960 (model 1909) and Windows 10 KB4557957 (model 2004) cumulative updates.
It’s value noting that Avast lately launched an replace with an identical bug that stops apps from working and following error message is displayed:
- Windows can not discover ‘C:Program Files (x86)Microsoft OfficerootOffice16EXCEL.EXE’. Make certain you typed the title appropriately, after which strive once more.
However, customers famous that they’ve this drawback when attempting to launch apps with out Avast software program:
“I don’t have Avast installed on my machine,” one person noted. “No, not running Avast on the machine,” one other person added.
A Microsoft neighborhood volunteer confirmed that it is a “known problem” with Windows 10 replace and customers can repair it by tweaking Registry entries.
To repair “Make sure you typed the name correctly, and then try again” error, you may strive these steps:
- Open Windows Registry (regedit).
- In Registry Editor, navigate to the next path:
- ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution folder
- Rename the folders of the apps that don’t work. For instance, rename “Chrome.exe” to “BackupChrome.exe”.
- Restart the pc.
Based on reviews, each Windows 10 cumulative replace and Avast replace are breaking down the apps.
If the issue persists and also you don’t use Avast, you can even uninstall Windows 10 cumulative replace KB4560960 or KB4557957.
To take away the replace, open up the Settings app after which click on ‘Update & Security’. From Windows Update pane, click on ‘View update history’ then ‘Uninstall updates’ and eventually choose ‘KB4560960’ should you’ve model 1909 and KB4557957 should you’ve model 2004.
If you utilize Avast, you’ll have to replace this system to the most recent model, which resolves the bug, in response to the corporate.