MC7304 detected as 3 devices in device manager and won't activate systematically as OS login

IoT Modules MC/EM Series
1

with whitelist on thinkpad x230, i installed MC7304 to complete the WWAN functionality.
it does show in device manager, but 3 times as 3 devices, only 2 can login to carrier service but it is not easy to see which ones are except trying to disable others to see the results.

the most boring is that the device will not show in device manager and login to carrier service systematically after OS login,
sometimes it take quite a moment to show later, sometimes it shows as login to OS, but it is always disactivated, not being activated by clicking the icon. to make it, it should firstly to to airplane mode (either way to disable radios), then disable airplane mode, likewise disabling radios and reenable radios so that it can login to carrier service.

there was earlier copy of OS that can login systematically to carrier service after upgrading driver 4836 and patch GPS firmware. but it doesn’t work any more after reinstallation of OS.

driver version 5087; OS win10 22h2

2

Will you consider to downgrade the OS?

How about other driver version?
https://source.sierrawireless.com/resources/airprime/software/airprime-mc-series-windows-drivers-qmi-build-history/

3

driver version 5087 as indicated, same issue with 4836.

the only time it did work correctly to login carrier after OS login: initially driver 4836 then update to 5087 and patch firmware and patch PGS.

which OS is tested? reinstall OS to try is time costly.

4

will you install the earlier copy of OS?

how about other older version?

5

the earlier cppy was the same version 22h2.

no older than 4836 tried.

6

but you say earlier version has no problem, which one is correct?

will you try older version?

7

i stated earlier copy not earlier version. it was the same version, installed previously but crashed due to wifi driver.

no intrest to try older version if no confirmation by others.

there are numerous issues on the forum that are similar to mine.

8

please post the link and see if there are solution there

BTW, did you check AT!GSTATUS? and see if there is registration issue?

Lastly, I still don’t quite understand why earlier copy is working fine…

9

who knows…

dont see there is soluton on the forum

10

You should be the one to know as you are doing the experiment with those earlier copy

did you check AT!GSTATUS? and see if there is registration issue?

11

same version OS, same version of driver. why should it be known to user?
are they open source?

12

Why you cannot use earlier copy then?
Have you checked with microsoft what is the difference?
Is the problem related to wifi driver?

did you check AT!GSTATUS? and see if there is registration issue?

13

see previous post pls. earlier copy of OS crashed !

no idea about AT!GSTATUS? or how to do it

14

Have you asked microsoft why it crashes?

You can use tera term to open modem port to type AT command

15

microsoft will say a lot of reason of crash: hardware failure, power loss, file crash etc…anyway it is indeed that window OS is easy to crash, mostly it requires to restart for some reason.

16

Then no idea if you cannot find out the difference on the OS…
Also no idea why your Windows OS is easy to crash

Anyway, you might debug by AT command

Good luck!

17

go to ask microsoft why, as there are so many !