Reply to thread

Message

<blockquote data-quote="SeriousHoax" data-source="post: 989284" data-attributes="member: 78686">There was a cumulative preview update which is the root cause of this issue. I don&#039;t know why .NET Framework 3.5 fixes it for affected users but that&#039;s how it is at the moment. Not everyone is having the issue. Looks like there&#039;s no update from Microsoft yet fixing it. So the update that was installed on your system on May 12 is not the fix for this. This was also installed on mine along with Patch Tuesday. There is something like KIKR fix or something, I forgot the term. MS sometimes pushes emergency fixes via that without releasing a dedicated update. They pushed this fix to users before patch Tuesday but looks like it didn&#039;t install in many people&#039;s device. So those who installed the preview update but don&#039;t have this mscore.dll issue probably received that emergency fix. Most if not all who didn&#039;t install the preview update don&#039;t have this issue.</blockquote>

[QUOTE="SeriousHoax, post: 989284, member: 78686"] There was a cumulative preview update which is the root cause of this issue. I don't know why .NET Framework 3.5 fixes it for affected users but that's how it is at the moment. Not everyone is having the issue. Looks like there's no update from Microsoft yet fixing it. So the update that was installed on your system on May 12 is not the fix for this. This was also installed on mine along with Patch Tuesday. There is something like KIKR fix or something, I forgot the term. MS sometimes pushes emergency fixes via that without releasing a dedicated update. They pushed this fix to users before patch Tuesday but looks like it didn't install in many people's device. So those who installed the preview update but don't have this mscore.dll issue probably received that emergency fix. Most if not all who didn't install the preview update don't have this issue. [/QUOTE]

Verification