Support Board
Date/Time: Sat, 07 Mar 2026 06:43:36 +0000
[User Discussion] - Can't access app
View Count: 191
| [2026-01-20 16:05:06] |
| cmack1011 - Posts: 188 |
|
My Desktop SC icon no longer worked (tried running as admin - did not work, etc), so I tried reinstalling the app, but I keep getting this error (I sent you the log file). I'm using the app on Macbook M3 with Parallels. Please advise.
|
Attachment Deleted.  Screenshot 2026-01-20 at 9.52.33 AM.png / V - Attached On 2026-01-20 15:55:13 UTC - Size: 90.71 KB - 39 views Screenshot 2026-01-20 at 9.52.26 AM.png / V - Attached On 2026-01-20 15:55:21 UTC - Size: 205.24 KB - 38 views |
| [2026-01-20 17:57:55] |
| John - SC Support - Posts: 44982 |
|
The "Installation Path" as defined in the install software is showing as just "SierraChart". This should be the full path to the location on the drive to install the software. We do not know how that translates with regards to Parallels. This is something you need to ensure is correct. Otherwise, use the "Zip Installer" to install the software. Refer to the following: Software Download: Sierra Chart Zip Installer For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-20 18:47:45] |
| cmack1011 - Posts: 188 |
|
So, I copied the zip file, pasted it into the C drive, extracted all the files, and the app still does not open?? The ARM version of SC can open just fine, but the 64 version does not which is the version I have been using on Parallels because I was told it could now be used with MACOs. Has something changed with the 64 version that it no longer works on Parallels? Im going to need to connect with someone live on this as it has completed arrested my ability to work. I'll pay for someone's time to do so Date Time Of Last Edit: 2026-01-20 19:03:14
|
| [2026-01-20 21:36:12] |
| John - SC Support - Posts: 44982 |
|
There was an issue that was posted about on the Support Board. The issue was related to an update to Windows 11 on Parallels. Refer to the following: Sierra Chart Not Loading Cant open sierrachart 64 version (non arm version) For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-20 22:23:40] |
| cmack1011 - Posts: 188 |
|
THose posts appear to be "all over the place"? Not sure where to start on approaching this? Are MacOS users now back to having to use the SC_ARM version (In which case I lose 4 months of custom work). Do I update WIN11 and Parallels or "down-date" them? Is there any consensus on what is going on?
|
| [2026-01-20 22:31:30] |
| John - SC Support - Posts: 44982 |
|
In the end - we really do not know. We just know that there was an issue, as it was found to be something with Parallels. We have set this as a "User Discussion" in the hopes that others that use Parallels on a MAC can give you some insight as to how to resolve this. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-20 23:45:17] |
| cmack1011 - Posts: 188 |
|
Ok, so an issue with Parallels narrows it down. Is it possible that now the v64 just no longer works with Parallels because it was not originally designed to do so, and that whatever modification you did to make v64 work previously has now "expired" and we now have to all go back to using the ARM version?
Date Time Of Last Edit: 2026-01-20 23:56:33
|
| [2026-01-21 00:26:07] |
| cmack1011 - Posts: 188 |
|
So, I plugged the group conversation into AI and this is what is spit out. Does any of this make any sense? Yes — this adds decisive insight, and it actually closes the loop on what’s happening. We can now say this with confidence: This is a Windows-on-ARM (Prism) regression interacting with Parallels, not a Sierra Chart bug, and not something you can reliably “fix” long-term by configuration. Let me explain why this second thread matters and what it changes. ⸻ What this new thread definitively confirms 1️⃣ The trigger is a Windows 11 update affecting Prism (x64 → ARM translation) Multiple independent confirmations: • x64 Sierra Chart worked for years • A specific Windows update window (mid-Nov → mid-Dec) breaks x64 UI launch • Rolling back Windows updates restores x64 • Updating again breaks it again This is textbook emulation-layer regression. The speculation about Prism is no longer speculation — it’s consistent with: • Behavior • Timing • Reproducibility • Cross-user reports ⸻ 2️⃣ The behavior is exactly what you’d expect from a CPU-feature mismatch Key clue (this is the smoking gun): “Hide Newer Emulated CPU Features (x64 apps only)” That setting exists specifically to deal with: • AVX / extended instruction exposure • ABI differences • Apps that mis-detect CPU capability and crash or hang during startup And note: • Some users cannot even access this setting under Parallels • Which means Parallels is locking or abstracting that layer So you have: • macOS (ARM) • Parallels virtualization • Windows 11 ARM • Prism x64 emulation • Sierra Chart x64 detecting CPU features That’s five layers where one change breaks the chain. ⸻ 3️⃣ Sierra Chart Engineering’s responses are very telling They consistently say things like: “There have not been any changes in Sierra Chart that would cause this.” “We do not know where the issue is — Parallels, Windows, or macOS.” That’s not deflection — it’s accurate. From their point of view: • ARM build works • x64 build works on native x64 Windows • x64 build fails only on Windows-ARM-via-Parallels That makes it out of their control. This is also why their only actionable response is: “If we have the source code, we can build the studies for ARM64.” That’s not a workaround — it’s an architectural direction. ⸻ Why uninstalling Windows updates “fixes” it (but isn’t viable) Rolling back Windows updates: • Restores an older Prism behavior • Hides newer CPU features • Avoids the problematic detection path But this is not sustainable, because: • Security updates will keep reintroducing the change • You cannot freeze Windows indefinitely • Parallels may re-enable features anyway Several users already hit this dead end. ⸻ Why ARM Sierra Chart is the stable equilibrium This thread confirms something important: Every path that keeps x64 alive is temporary. Every path that uses ARM64 is stable. Notice the pattern:Path Result x64 + updates breaks x64 + rollback works temporarily x64 + hidden CPU features works sometimes ARM64 native works consistentlyCritical distinction for you (this is where your situation differs) Many users are stuck because: • They do not have source code for custom studies • Vendors must recompile for ARM You are not in that position. You: • Own GS2 / FAST / ProbFAST source • Already rebuild frequently • Control the entire pipeline So what’s a disaster for others is manageable for you. ⸻ What this changes (and what it does not change) ❌ It does NOT mean: • Sierra Chart is abandoning x64 • ARM is “experimental” • Your current GS2 work is invalid ✅ It DOES mean: • x64 on Apple Silicon via Parallels is now structurally fragile • ARM64 is the forward-compatible path • Recompiling is unavoidable if you want long-term stability ⸻ Practical, grounded conclusion This second thread confirms our earlier diagnosis and strengthens it: Do not spend time trying to stabilize x64 Sierra Chart on Parallels. Treat ARM64 Sierra Chart as the correct runtime on Apple Silicon. Anything else is chasing a moving target controlled by Microsoft + Parallels. ⸻ What I recommend next (no commitment yet) Not action — just planning: 1. Accept ARM64 as runtime 2. Inventory which DLLs you actually need 3. Decide: • ARM-only (simplest) • Dual-target (ARM + x64, if you still run native Windows elsewhere) When you say “go”, we can do this cleanly and deliberately — no rushed port, no broken GS2 state. You were absolutely right to pause and troubleshoot first. |
| [2026-01-21 15:26:27] |
| John - SC Support - Posts: 44982 |
|
For once, what AI responds with does make sense. It is telling you what we have stated. This is an issue between the Windows 11 version and Parallels. This has nothing to do with the Sierra Chart executable. The AI recommendation is to use the ARM version. We can not comment any further. We do not use Parallels ourselves. We know nothing about that environment. There is nothing wrong with our software, so there is nothing we can do. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-21 17:35:14] |
| cmack1011 - Posts: 188 |
|
Well, since I now have to go back to the ARM version, which I though I would never have to do, I have to convert 4 months of custom work to ARM (if even possible), but I also do not want to delete the non-ARM work I have done or mix the two sets of work. Thus, is it possible to have two separate installations of SC so that they are not sharing the same data files, etc? Otherwise, this is going to get very complicated and messy. So it would look like: C:\SierraChart_ARM\ SierraChart_ARM64.exe Data\ GS2_Feature_Exporter_v12_19_VAP_FINISHDELTA_RECENCY.dll FAST_Universal_Model_v8_GOLD_FINAL_HANDOFF_PATCHED.dll ProbFAST_GS2_Targets_RealModels_v12_19_Fixed3.dll C:\SierraChart_x64\ SierraChart_64.exe Data\ GS2_Feature_Exporter_v12_19_VAP_FINISHDELTA_RECENCY.dll FAST_Universal_Model_v8_GOLD_FINAL_HANDOFF_PATCHED.dll ProbFAST_GS2_Targets_RealModels_v12_19_Fixed3.dll |
| [2026-01-21 18:50:24] |
| John - SC Support - Posts: 44982 |
|
You can have as many installations of Sierra Chart as you want on a single computer. The only limitation is going to be data (which is a limit of 3 installations getting data at the same time). Refer to the following regarding the data limit: Denali Exchange Data Feed: Denali Exchange Data Feed Connections on Same Computer Simultaneously Refer to the following for how to install another Sierra Chart: Using Multiple Data and Trading Services at the Same Time: Step-By-Step Instructions to Install Multiple Copies of Sierra Chart For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: