V3 - working at home but not at work!?

Speckle Help
,
1

Moved to the v3 connectors & world of workspaces for my home-brew testing these last few days, and set about to do the same at work today - but ran into a blank panel (in Revit 2026.2) - raised a webchat, thinking it might be because the .exe was alerting me about running as admin (which I wasn’t) and Nikos (sp? apologies) suggested it might by pesky PyRevit, so I went on a deep purge of my machine - uninstalled/reinstalled the speckle stuff - but still, blank.

Finding a similarly titled, but differently posed thread, HERE prompted me to go fish for a log, and found this indecipherable wall of words:

2025-09-01 17:46:55.511 +01:00 [ERR] An unhandled Exception occured
System.InvalidOperationException: Webview Failed to initialize
—> System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
at System.Windows.Threading.Dispatcher.g__ThrowVerifyAccess|7_0()
at Microsoft.Web.WebView2.Wpf.WebView2Base.get_CoreWebView2()
at Microsoft.Web.WebView2.Wpf.WebView2Base.<>c__DisplayClass32_0.<g__Init|0>d.MoveNext()
— End of inner exception stack trace —
at Speckle.Connectors.Revit2026.Plugin.RevitControlWebView.OnInitialized(Object sender, CoreWebView2InitializationCompletedEventArgs e) in //Connectors/Revit/Speckle.Connectors.Revit2026/Plugin/RevitControlWebView.xaml.cs:line 60
at Speckle.Connectors.Revit2026.Plugin.RevitControlWebView.<>c__DisplayClass2_0.<.ctor>b__1() in //Connectors/Revit/Speckle.Connectors.Revit2026/Plugin/RevitControlWebView.xaml.cs:line 25
at Speckle.Connectors.DUI.Bridge.TopLevelExceptionHandler.<>c__DisplayClass5_0.b__0() in //DUI3/Speckle.Connectors.DUI/Bridge/TopLevelExceptionHandler.cs:line 44
at Speckle.Connectors.DUI.Bridge.TopLevelExceptionHandler.CatchUnhandled[T](Func`1 function) in //DUI3/Speckle.Connectors.DUI/Bridge/TopLevelExceptionHandler.cs:line 61

What’s odd is that everything at home is working fine - and I don’t believe we have any kind of particularly prickly policies in place that might be locking down Speckle (I definitely had v2 products working before)

any ideas/suggestions, please?

2

Hello, have you checked any firewall policies at your workplace that may be blocking the add-in?

1 Like
3

yep, none. And the Speckle connector launches and connects just fine in 2023.1.2 on the same machine.

Nor is it a 2026.2 issue as its runs at home.

It also wasn’t Kinship or Xrev (the only addins that I have work that I don’t have at home) having removed them to test.

It’s also not my (local admin) user account, having just tried as another user = same machine, same scenario (2023 launches, 2026 does not) ?

my WebView2 is also bang up to date.

I’m going to try a second work machine later today to see if it runs on that - which, if it does, probably means there’s a gremlin still lurking in my machine… but what, or where, remains a mystery.

4

^second machine tested, exact same result & same (WebView related) log message.

Our IT checked our AV (Sophos) wasn’t blocking it
(which was kind of a given, since Speckle runs on 2023)

The only variable remaining (that I’d somehow forgot to mention):
work machine = Win11
home machine = Win10

…so given Microsoft’s past record of breaking things; perhaps they’ve changed something that doesn’t play nice with whatever Autodesk changed in Revit 2026?

I’d be interested to know if anyone’s successfully running v3 on 2026.2 on a Win11 machine.

5

I had an issue running the connector on Revit 2026, exact same WebView2 issue. In my case, resetting my laptop resolved the issue.

It will work in Revit 2023 because 2023 doesn’t use WebView. It uses CEF which is a different technology.

Since it works on your machine at home, this indicates something is different in your work machine.

  • Check for group policies that restrict WebView2/embedded browser
    components
  • Antivirus software that interferes with WebView2 initialization

Also, do you have Autodesk Data Exchange installed? That may be conflicting as well. Try disabling/uninstalling that and see if it changes anything.

1 Like
6

“good” to hear (you got it working**) but when you say “reset”, do you mean a ground-up windoze* rebuild??? I’m not against such heavy handed actions (if needs be) but I’d obviously prefer to avoid that…

but, i guess, seeing as it works “here” but not “there” = must mean its a system/environmental reason of some kind

**Q. are/were you running Win11?

  • since that’s the “only” differentiator that we can identify/think of right now (besides hardware, but that seems nonsensical, given '23 runs fine, and I have v3 running happily on a 6th gen i7 here, so my 13th gen i9 at work shouldn’t be having issues.

I’m fairly certain, thanks to the log, it is 100% an issue with WebView, but understanding what that means (certainly in terms of which app/service is potentially “hijacking” it, ahead of speckle) remains the mystery.

**If it ends up being our IT’s monitoring system (n-able) then it might mean an early bath Speckle (boo)

7

I was using Windows 11. I did a factory reset of my laptop.

I remember installing some preview features of Edge, which i assumed caused this issue. Couldn’t revert it hence reset my laptop.

8

I had the exact same issue, and the same log info as you.

This time, removing pyrevit and Data Exchange actually worked for me.