Math applications not running in Windows 11

Anonymous
2023-03-19T11:06:58+00:00

Greetings,

I am having a tedious issue with a couple of Math applications on a brand-new Windows 11 desktop. Microsoft Mathematics and MaThType 6.9d show the splash screen but then nothing happens: they do not show up. Net Framework 3.5 is turned on and Windows update does not show anything left to install. Here are the device and Windows specifications.

Processor Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz 3.60 GHz
Installed RAM 8.00 GB
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Edition Windows 11 Pro
Version 21H2
OS build 22000.1696
Experience Windows Feature Experience Pack 1000.22000.1696.0

On other PCs - both Windows 11 and Windows 10 - I do not have this issue. Because it affects two Math applications, I guess it must be related to a common cause. But what could it be? I'm really stuck if I cannot use them, in particular mathtype.

Thank you in advance for any help.

Windows for home | Windows 11 | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

46 answers

Sort by: Oldest
  1. Ramesh 181.9K Reputation points Volunteer Moderator
    2023-03-20T13:46:43+00:00

    The ProcMon log you uploaded is the previous PML log (3rd one, I think). The file size and date modified are the same. If you rerun the trace, please save all events.

    And the error in WinDbg seems to be gone after replacing the module. But the "second chance" error occurs, which I can't repro here. This is from my WinDbg window.

    * * * * *

    com\oleaut32\stdtypes\pictobj.cpp(3103)\ole32.dll!00007FFE3B1E4EB6: (caller: 00007FFE3B1E59D2) LogHr(3) tid(10c) 8007029C An assertion failure has occurred.

    com\oleaut32\stdtypes\pictobj.cpp(3103)\ole32.dll!00007FFE3B1E4EB6: (caller: 00007FFE3B1E59D2) LogHr(4) tid(10c) 8007029C An assertion failure has occurred.

    com\oleaut32\stdtypes\pictobj.cpp(3103)\ole32.dll!00007FFE3B1E4EB6: (caller: 00007FFE3B1E59D2) LogHr(5) tid(10c) 8007029C An assertion failure has occurred.

    com\oleaut32\stdtypes\pictobj.cpp(3103)\ole32.dll!00007FFE3B1E4EB6: (caller: 00007FFE3B1E59D2) LogHr(6) tid(10c) 8007029C An assertion failure has occurred.

    ModLoad: 000000002a4c0000 000000002a536000 AppSkin1.dll

    ModLoad: 000000002a540000 000000002a5b6000 AppSkin1.dll

    ModLoad: 000000002a4c0000 000000002a536000 C:\Program Files\Microsoft Mathematics\AppSkin1.dll

    ModLoad: 000000002a4c0000 000000002a536000 C:\Program Files\Microsoft Mathematics\AppSkin1.dll

    ModLoad: 00007ffde6f20000 00007ffde6f44000 C:\WINDOWS\system32\msctfui.dll

    ModLoad: 00007ffe36430000 00007ffe36563000 C:\WINDOWS\SYSTEM32\CoreMessaging.dll

    ModLoad: 00007ffe33600000 00007ffe3396c000 C:\WINDOWS\SYSTEM32\CoreUIComponents.dll

    ModLoad: 00007ffe355b0000 00007ffe355b7000 C:\WINDOWS\SYSTEM32\shfolder.dll

    ModLoad: 00007ffe382d0000 00007ffe38312000 C:\WINDOWS\SYSTEM32\SspiCli.dll

    ModLoad: 00007ffe361e0000 00007ffe36423000 C:\WINDOWS\SYSTEM32\dcomp.dll

    * * *

    And someone else was facing the same issue.

    Looks like a corrupted .NET installation is the root cause.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-03-20T14:11:27+00:00

    Apologies for the mistake. Here is the correct log file https://1drv.ms/u/s!AgBRQ6GYkPGlgySSzLJF-BuvOsx_?e=ZZfXnW

    From the post of 2018 I access a download link

    https://www.microsoft.com/en-us/download/details.aspx?id=22

    I get the file dotnetfx35setup.exe but when I launch it - with Admin rights - nothing happens.

    Was this answer helpful?

    0 comments No comments
  3. Ramesh 181.9K Reputation points Volunteer Moderator
    2023-03-20T14:43:37+00:00

    Running these commands...

    certutil -hashfile C:\Windows\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll sha256 
    
    certutil -hashfile C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9680_none_88e394a52fab6222\msvcr80.dll SHA256 
    
    certutil -hashfile C:\Windows\Microsoft.NET\Framework64\v2.0.50727\diasymreader.dll SHA256 
    

    ... show the following outputs, respectively:

    SHA256 hash of C:\Windows\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll:

    689b34214b4929a6aa894c094b98d6afac2c8cfc021c366a83f47fa947b1a5d9

    CertUtil: -hashfile command completed successfully.

    SHA256 hash of C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9680_none_88e394a52fab6222\msvcr80.dll:

    e7d797dc4d9cd131e4aec03d3315de181e5dc031e4435acb426dbaf5bd678fe2

    CertUtil: -hashfile command completed successfully.

    SHA256 hash of C:\Windows\Microsoft.NET\Framework64\v2.0.50727\diasymreader.dll:

    adb880576eb02f96f77eeaafdff0992dee531aa5eb04a600db563c3f3a159b09

    CertUtil: -hashfile command completed successfully.

    msvcr80.dll was the last file accessed, per the call stacks, after which the WER crash occurred. Pls compare the outputs on your system.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-03-20T14:53:32+00:00

    Here are the three outputs

    SHA256 hash of C:\Windows\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll:689b34214b4929a6aa894c094b98d6afac2c8cfc021c366a83f47fa947b1a5d9
    CertUtil: -hashfile command completed successfully.

    SHA256 hash of C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9680_none_88e394a52fab6222\msvcr80.dll:e7d797dc4d9cd131e4aec03d3315de181e5dc031e4435acb426dbaf5bd678fe2
    CertUtil: -hashfile command completed successfully.

    SHA256 hash of C:\Windows\Microsoft.NET\Framework64\v2.0.50727\diasymreader.dll:adb880576eb02f96f77eeaafdff0992dee531aa5eb04a600db563c3f3a159b09
    CertUtil: -hashfile command completed successfully.

    Was this answer helpful?

    0 comments No comments
  5. Ramesh 181.9K Reputation points Volunteer Moderator
    2023-03-20T15:21:30+00:00

    The hashes match. Some more ideas:

    1. Try this REG file. This is to remove the "SQMSelected' value, which doesn't exist in my system. As you can see from the following entries, the SQM thing may have something to do with the crash.

    1. The x86 version of MS Math is available here if you wish to try it.
    2. Set the "Program Compatibility Assistant Service" service to Manual start. Click Start to start the service manually.
    3. Access MathApp.exe properties and enable the Windows 7/8 compatibility mode.

    Was this answer helpful?

    0 comments No comments