I'm experiencing troubles with MS Office 2010 64-bit, which may be or may not be related with updating to v11. I had older version of ESU installed (ver 9?) and decided to upgrade to ver.11. I didn't uninstall and fully reinstall it but just updated .NET bypasser. A couple minutes after MS Word ceased to start without any errors or logs in System events -- it just didn't start when I click the application icon or try to open Word document. However, all other Office applications (Excel, PowerPoint etc) had been working fine. I tried to repair the Office installation it by running setup.exe from my Office 2010 DVD, but only got some error about missing/corrupted OSETUP.DLL (despite it was in the same directory). I tried to copy the files to my HDD and launching installer once again, but it didn't helped much. As I couldn't even uninstall MSOffice at that moment, I just reverted back to system partition backup from October 2020, and checked if Word is working and installer is launching without errors -- they were working fine. Then I again updated ESU to v11 without removing older version first, and got the same problem as before with Word and setup.exe not launching. So I had to roll back older backup once again and temporary postpone updating ESU patch. I wonder if anyone else had the same troubles, or there's some unfortunate coincidence with my system behaving like that.
Hello in the December update I did not receive the one for .net framework 4.8 I also seem to have read that some people are looking to download framework 5.0 manually is it essential for all? If so where can I find this download? On the other hand I downloaded the Bypass v11 without having downloaded the v10 there are no consequences? thank you in advance for your help
Hello Abbodi et Enthousiast I am with the BypassESU v9 I must go directly to BypassESU v11 Or go first to BypassESU v10 then later to BypassESU v11 Have a nice day and merry christmas
@fch1993 you cannot use Wim-Integration on wimfile to update BypassESU versions (because it only add new options, it does not remoe old vrsions) therefore, it can be used only on clean (unpatched) install.wim
It may be somewhere here, but this allows esu updates to be installed but they have to be manually installed?
This morning the Adobe Photoshop CS6 program was not working in my PC. I thought that some module of the program or some registry key (I usually clean it often) was damaged. I have deleted the program, I have reinstalled it again, but I still couldn't open it, until I remembered the installation I did yesterday of BypassESU-v11. After disabling the .NET Bypass module, everything worked fine again with the new Photoshop installation. I am warning you because .NET Bypass continues to give problems if it is activated even in its most recent version. Best regards!
I was thinking that PreferExternalManifest registry cause issues for some system progams/icons sadly, it affect other programs when that value is active, for unknown undocumented reason, some programs require external .3.manifest file to work properly the manfest can be for exe or dll files i re-added the warning/recommendation regarding .NET 4 Bypass (it should be installed only when new .NET 4 updates are available, and removed afterwards)
What does it do? How does it compare to the .net45/472/48? Can I leave it installed? Will it cause problems to Windows 7 Pro 64bit or Office 2016 32? Please advise and detail out for the community? Kind regards,
Unless some app specifically asks for it, you don't need it but you can still keep it, it will not affect Windows or Office