Skip to main content

Connect:Amp (C100) stuck on update – Error 27 / StubReason = “secreg” – secure registration won’t complete

  • November 5, 2025
  • 3 replies
  • 52 views
S

Hi everyone,

I’ve been working with Sonos Level 2 Support on this issue (case **********), but I wanted to check if anyone here has found a working solution for this situation.

Device details

  • Model: Sonos Connect:Amp (C100) – second-hand unit

  • Serial number: ***************

  • Software version: 78.1-52020 (S2 16.1.1)

  • Hardware version: 1.17.3.1-2.1

  • Accessible locally on port 1400

  • Internal pages responding: /status/zp and /support/review

  • Shows:

    StubReason: secreg QuarantineReason: –

  • Added to my Sonos system, but playback is blocked until the update and secure registration complete.

What I’ve tried so far

  • Multiple update attempts through different isolated networks:

    • iPhone hotspot → Mac internet sharing → TP-Link C1200 router → Connect:Amp via Ethernet

    • Also tested on ZTE Wifi Silbo, Linksys mesh + Starlink (bypass mode)

  • The update starts normally but fails at the end with Error 27 (also Error 1013 on macOS).

  • The Connect:Amp clearly has internet access (download starts), but it seems to reject or fail to validate the firmware package — likely due to expired TLS certificates or an outdated trust store.

Support feedback
Sonos L2 confirmed the device is stuck in a “secure registration” state (StubReason = secreg) and that the re-registration can only succeed after a successful firmware update — which, unfortunately, always fails.

My question to the community
Has anyone encountered this “secreg” + Error 27 loop and found a way to:

  • either manually update or flash a C100 Connect:Amp (S2) beyond version 78.1-52020, or

  • trigger a secure registration refresh when the update can’t complete?

Any technical insights, known workarounds, or hints on whether Engineering can push a forced firmware update to unlock the device would be greatly appreciated.

Thanks in advance,
Lars

 

Moderator Note: Removed case and serial number. Modified in accordance with the Community Code of Conduct.

3 replies

Stanley_4
  • Stanley_4
  • Lead Maestro
  • November 5, 2025

Try turning off any network or DNS filtering you have enabled.

Any chance you can visit a friend that has a cable/fiber/DSL network connection to see if that works?

S
  • SoLars
  • Author
  • Contributor I
  • November 7, 2025

Hello @Stanley_4,

Thank you for sharing your opinion.

I asked a friend with a cable/fiber optic/DSL network at home to give it a try, and he just let me know that:

“I get error message 27 on Android and 1030 when I try to update from the Windows app.”

Unfortunately...no success.

Any other suggestions are welcome.

 

S
  • SoLars
  • Author
  • Contributor I
  • December 16, 2025

Final update / conclusion

Thanks to everyone who contributed ideas and suggestions.
I want to share the final outcome of this case after further investigation together with Sonos Level 2 Support and Engineering.

Summary of the findings:

  • The Connect:Amp (C100) consistently failed firmware updates with Error 27.

  • Internal diagnostics showed that:

    • the device repeatedly comes online as unregistered

    • certificate validation consistently fails

    • secure TLS connections (port 1443) are rejected

    • during update attempts the player repeatedly drops off and reappears via SSDP/MDNS

  • As a result, the UpdateClient is unable to establish a secure session and every update fails in stage 2.

  • This behavior was reviewed and confirmed by Sonos Engineering.

The key point is that:

All Sonos recovery, reflash, and forced firmware update procedures depend on a successful secure registration.
Because a secure connection can never be established in this case, these recovery paths are technically unavailable.

After escalation, Sonos concluded that the most likely root cause is a hardware failure in the secure storage / TLS communication component of the Connect:Amp.
This type of failure:

  • allows the device to appear normal on the local network,

  • but prevents any secure cloud communication, provisioning, or firmware updates,

  • and is not repairable within the Sonos service model.

Sonos does not offer repair or installer-based recovery for this scenario.
As a goodwill gesture, a discount coupon toward a replacement Amp was offered, and the case has now been closed.

Important note for others experiencing similar symptoms:
If you have a Connect:Amp (C100) showing:

  • StubReason = secreg

  • repeated Error 27

  • failed secure connections on port 1443
    this is very likely not a network or configuration issue, but an unrecoverable secure-hardware failure.

Hopefully this conclusion helps others reach clarity faster.

Best regards,
Lars

    Terms & ConditionsCookie settingsAccessibility statement