What does NTSTATUS 0xC0000300 (STATUS_NOT_SUPPORTED_ON_SBS) mean?

 
Previous Next
STATUS_SERVER_SHUTDOWN_IN_PROGRESS STATUS_WMI_GUID_DISCONNECTED

STATUS_NOT_SUPPORTED_ON_SBS

This is historical product-edition gating, not generic feature absence

STATUS_NOT_SUPPORTED_ON_SBS names a specific historical product family: Windows Server 2003 for Small Business Server. The public status text does not identify the operation that returned it, so the API or server component must be captured. The useful distinction is that the operation was rejected because of the SBS product context, not simply because an entry point was missing.

Windows exposes suite information through OSVERSIONINFOEX.wSuiteMask and RtlGetSuiteMask. Microsoft documents VER_SUITE_SMALLBUSINESS and VER_SUITE_SMALLBUSINESS_RESTRICTED, while also warning that the Small Business bit can remain set when SBS was once installed and the system was later upgraded. Protocol product-behavior tables additionally distinguish Small Business Server product identities. This is why a raw suite bit should be logged together with actual OS version and product identity.

When investigating old binaries, installers, management agents, or server roles, record the exact function returning the status, OS version, architecture, suite mask, and deployment history. Do not “fix” the error by renaming an executable or forcing a compatibility layer: edition checks can reflect licensing or supported topology assumptions in legacy software. Windows Small Business Server 2003 is also long out of support, so reproducing on a supported replacement platform may be more informative than patching around the historical gate.

What to inspect

  • Capture the exact API/component that performs the SBS gate.
  • Record OS version, product identity, and suite mask together.
  • Treat stale edition-detection logic in legacy software as a separate possibility from an intentional product restriction.

References

Looking for a different code? Search another status or error code.