@rosmer just tossing things up the air here, but I'd look at your Jamf Connect profile and see if everything is kosher with it. Are there any in-office Jamf Connect users?  How do they perform? 

Thanks for looking @steve_summers!

Everything had been working correctly so far for these users, with the profiles as configured and logging in. The users are actually in-office too, they had just brought their Macbooks home for the evening.

I've managed to borrow one for a moment and uninstalled Connect, then reinstalled, but it goes right back to hanging the moment the login window tries to load.

We're seeing the same behavior here. Just started this week. Have you had any luck with a solution?

We just started seeing this too in the past few days.

Only a few seconds at login window to turn WiFi off (and see our Local Login button) before the login window hangs. Resetting authchanger (/usr/local/bin/authchanger -reset) got the login window back to default and users could log in, but setting authchanger back to jamf connect (/usr/local/bin/authchanger -reset -JamfConnect) brought the problem back. Continuing to troubleshoot when I can get my hands on one... 

We found that this was only affecting devices on MacOS 12.3. We updated to 12.6 on those devices and everything is working as normal now. 

Thanks for the lead @llambert! I will check out the OS version and give updating a try.

Can also confirm for us its 12.3 machines and OS update fixes it, but I'm trying to exhaust any simpler fixes or workarounds for people just running into this issue. Curious why it just seems to have started even if its only on 12.3 machines

@here, has anyone found a better workaround than wiping systems to 12.6.5 or higher to get rid of this problem? Jamf support mentioned to me in a ticket that is is related to to PI111513 but I can't seem to find any info in the Known Issues section. We usually deploy zero touch config systems leveraging JC/DEPNotify and this is a showstopper as we are having to wipe the system entirely first and update to 12.6.5 or above to bypass this problem (and therefore unable to drop ship the system to our new hires etc.)

Things I've tried so far:

• removing JC from PreStage and install later at login etc 
• install a previous version of JC

None of these seem to work as it really boils down to not having a 12,6.3 system (all of our pre-purchased systems come with 12.6.3 from our vendor unfortunately). Any found work around would be great!

Has anyone had a dataloss issue with this or is there a consistent workaround? Thanks!

The only fix I've had work is updating the OS past Monterey 12.3.

If you're quick enough at the login screen you should be able to click Local Login before the JAMF Connect window freezes and log in as a local administrator, then update the OS.

Done this way there should be no data loss, as a wipe of the computer isn't needed.