
Christian Treffler
61 discussion posts
Any feedback on this? Does anybody else have that problem?
Maybe a Microsoft update problem again?
I made some tests today. In February Miccrosoft installed two updates:
KB5050576 and KB5051974.
A system-image from February 2nd works fine. After starting Windows update now these two updates are installed:
KB5049621 & K85049981. It seems that the previous updates have been replaced.
And the observed issue is gone.

Christian Treffler
61 discussion posts
Thanks, that solved the problem. And I think I know how it broke:
I had the 'Microsoft Windows Desktop Runtime - 8.0.5 (x64)' installed. Sometime in the last weeks a Print&Scan utility from Brother installed an update and with that it installed 'Microsoft Windows Desktop Runtime - 8.0.13 (x86)'.
The '8.0.5 (x64)'-version was still there, but it seems that DisplayFusion could not use it anymore.
I installed the 'Microsoft Windows Desktop Runtime - 8.0.13 (x64)' which you recommended and now DisplayFusion works again.
The x86 and x64 runtime are now installed side-by-side because the Brother utility needs the x86-version.