Good news !!
the new debug version of Chromium-for-windows-7 with previous sdk version fixes the issues on chromium 136 !!!
"I've built a new version 136.0.7081.0 that's identical to this release, except for reverting commit chromium/chromium@fca8e87.
This means the build uses Windows SDK version 10.0.22621.2428, so the issue shouldn't occur in this version.
https://github.com/e3kskoy7wqk/Chromium ... .packed.7z
https://github.com/e3kskoy7wqk/Chromium ... taller.exe
https://github.com/e3kskoy7wqk/Chromium ... 2868826546
Thanks Mr @Redfox for your valuable advice! And sorry, I don't receive notifications when you comment. I realize I haven't seen many of your messages, sadly
No, I don't have a backup. My Eee PC is too weak. I disabled backup.
Yes, the problem is probably KB4019990.
Sadly, I can't install KB4019990. I have an error message. I probably have a corrupted system. Please, can you help me repair my Windows OS? Apparently, there are special commands via CMD to repair Windows OS?
I found this software:
https://wureset.com/ made by @WUReset
and
https://www.bleepingcomputer.com/downlo ... ll-in-one/
Do you recommend installing these programs to repair my Windows OS and install KB4019990 to fix the Chromium 136 problem? ?
Mr @Catsxp, Mr @Redfox, Mr @E3kskoy7wqk just told me:
"I don't believe the root cause is related to d3dcompiler_47.dll at all. I initially discussed the d3dcompiler_47.dll issue here:
#47 (comment)
In fact, all builds I provided in
https://github.com/e3kskoy7wqk/Chromium ... /tag/debug already use Windows 7-compatible versions of d3dcompiler_47.dll, but the problem persists."
https://github.com/e3kskoy7wqk/Chromium ... 2868905692
So,
now I'm currently completely exhausted and tired from the stress and after testing several versions, so our wish please , it it doesn't tire too much Mr @Catsxp, we dream that the hero Mr. @Catsxp makes a special version of Catsxp for Windows 7 32-bit OS based on the previous SDK version, thanks!
https://github.com/e3kskoy7wqk/Chromium ... .packed.7z