SCP 6.11.3 stuck at 33% after rebooting

Rushdi Lv1Posted 2026-Aug-26 19:41

Has anyone come across the issue where, SCP 6.11.3 is stuck at 33% after reboot? This is a fresh installation of SCP.

By solving this question, you may help 875 user(s).

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Muhammad Abid Lv3Posted 2026-Aug-27 12:24
  
Yes — if you mean Sangfor Cloud Platform (SCP) 6.11.3, a boot/install process hanging around 33% after a reboot is something I’d troubleshoot as a SCP VM/resource or service initialization issue, rather than immediately assuming the installation is corrupted.

I checked the current Sangfor documentation, and 6.11.3 is an active SCP release. There is also a current Sangfor support article specifically showing that SCP 6.11.3 should be matched with HCI 6.11.3.

A few things I'd check first:

Confirm the HCI version

If SCP is deployed on HCI, verify the underlying HCI is also 6.11.3.
Sangfor's current guidance explicitly pairs HCI 6.11.3 with SCP 6.11.3.
Check SCP VM resources
CPU and RAM allocation.
Disk capacity and whether the SCP virtual disk is healthy.
Make sure the SCP VM isn't being constrained by HCI resource contention.
Open the SCP VM console
Don't rely only on the web interface.
Check whether the console is actually progressing, showing a service failure, or completely frozen at the same stage.

Check networking
Verify the management NIC/VLAN.
Confirm the SCP IP is still reachable after reboot.
If possible, test both ping and HTTPS access.
Consider the image/package

If this is a fresh installation, I'd strongly consider re-importing/reinstalling from the official 6.11.3 VMA rather than spending too long troubleshooting a potentially bad image.

There are also newer 6.11.3 patches in circulation. For example, Sangfor's current documentation for Veeam integration references SCP 6.11.3 + col01, with a SP_SCP_fix_col01_6113 package.

One important distinction: if it reaches 33% only after the first reboot, rather than during the initial deployment, I'd want to see exactly what the 33% screen says. That can point to a very different problem.

If you can send me a screenshot of the SCP console stuck at 33%, plus your HCI version, SCP VM CPU/RAM, and whether SCP is installed as a VM on HCI, I can narrow it down considerably.

I Can Help:

Change

Board Leaders

YerkoUm...

Weekly Sharers

Eduardo...

Weekly Questioners