3129 and 3130 will not run on my PC

[seggins]

Running Windows 10 build 21376.

CumulusMX b.3122 runs perfectly, but neither 3129 nor 3130 will. I have no information from diagnostics etc because the program freezes my machine.
It appears that something introduced in 3129 has not suited my PC
Specification:
Summary
CumulusMX.exe
Process ID 16112
User seggi
Domain WINDOWS-JHF0500
Path F:\Tools\CumulusMX3122\CumulusMX\CumulusMX.exe
Memory Usage 62 MB
F:\Tools\CumulusMX3122\CumulusMX\CumulusMX.exe (16112)
Local 192.168.0.47:50847 ESTABLISHED Remote 213.171.193.5:21 (Querying... ) (FTP-data)
Local 0.0.0.0:8998 LISTEN

"Events" does not seem to be any help.
Can anyone help or suggest strategies?

Regards
John Say

[ConligWX]

would need to see the MXDIAGS logs really. can you zip up the logfile when you try loading 3129 or 3130 and post here.

[water01]

This is Windows Insider build of Windows 10 built only 3 days ago and released through the Developers Channel. https://blogs.windows.com/windows-insid ... ild-21376/

It is most unlikely that Mark Crossley the developer of these builds has any access to such a Windows 10 build. Now a lot changed in MX builds between 3122 and 3130 in terms of components within MX so the chances of those components being tested against such a new release of Windows 10 is remote in the extreme.

I suggest you revert to a standard release of Windows 10 such as 20H2 (Build 19042), because I am afraid that is the only way you are going get any support. I am running this release of Windows 10 and both MX 3129/3130 are running perfectly.

[f4phlyer]

David, you mention running 3129 and 3130. Just curious, how are the two isolated? I'd like to run CumulusMX on two 'Pi's" as I rebuild my Pi's with Buster. Do you have two consoles and or a WLL? Or do you just run two separate occurrences of MX?

I suggest you revert to a standard release of Windows 10 such as 20H2 (Build 19042), because I am afraid that is the only way you are going get any support. I am running this release of Windows 10 and both MX 3129/3130 are running perfectly.

You are spot on about support of MX on a beast as rare as the Win 10 Insider, but if it'll help, I run Win 10 insider on one of my Windows machines, I'm kind of courious so, I'll give it a quick try to see if it'll break.

[water01]

David, you mention running 3129 and 3130. Just curious, how are the two isolated? I'd like to run CumulusMX on two 'Pi's" as I rebuild my Pi's with Buster. Do you have two consoles and or a WLL? Or do you just run two separate occurrences of MX?

Bad use of English, I meant I ran 3129 when it was released and then 3130 when it was released and both versions ran without problems. I only have the one install.

[seggins]

Whereas it would be nice to be able to run the latest build of CumulusMX, I simply wanted to inform folks of the situation with the latest W10 iteration.
I am perfectly happy to be running MX 3122.
Regards
John

[ConligWX]

unless Mark can identify from the MXDiags logs what is going on with CumulusMX and Windows Developer, it wont be fixed, even in fact if it is a CumulusMX issue.

My guess is you would need to enable debugging for CumulusMX too and try and run it again, then post the logfile here for Mark to see what is happening. The information you have provided so far is not enough for a developer to go on.

[mcrossley]

Yep, please run Cumulus using the -debug command line parameter then post any log file produced in MXdiags.

[f4phlyer]

Ok, on my Win 10 "insiders build" -latest- started up fine and ran fine.

Only ran for a few minutes but no problems.

My "Extra_files" folder is outside the CumulusMX folder and I hadn't created it so that's why MX couldn't find files.

Attached the mxdiags

[seggins]

3131 does not start either.
I am unable to send any Diagnostic data because the program never starts. Could it be to do with Edge I wonder?
3122 runs perfectly as have all its predecessors.
Regards
John

[mcrossley]

Can you screen snip the Cumulus Window so we can see the error?

Edge is fine, many many people use it.

[SamiS]

3131 does not start either.
I am unable to send any Diagnostic data because the program never starts. Could it be to do with Edge I wonder?
3122 runs perfectly as have all its predecessors.

It is very hard to believe, that CumulusMX would hang so early, that it does not write anything to its log files. So if you start command prompt or powershell and run

cumulusmx.exe -debug

even if your computer hangs you should have some logs to send here on MXDiags folder.

[mcrossley]

Does the program window not open at all then?

[seggins]

That's correct. Now, because 3132 runs on the latest W10 release (21387), I suspect the previous W10 had some glitch or other that was preventing MX getting started.
All working fine now.
Onwards and upwards
Regards
John