PENDING Failed to wait for CcmExec service to be fully operational (0x80070005)

[bom2010]

Can someone help me to fix this issue as my picture attached. I already tried many solution i can find however it was worked.

Btw, someone have any tools to compatibility assessment before upgrade win 7 to win 10.

Thank everyone assist for me !

 

[bom2010]

 

[Prajwal Desai]

I have heard about this issue before. Some blogs suggest a quick workaround which is place a Start-Sleep command in directly after the Setup Windows and ConfigMgr step. This allows the client to fully initialize and work as expected.

Have you tried this earlier ?.

Powershell.exe -ExecutionPolicy Bypass -Command “Start-Sleep -s 120”

 

[bom2010]

I have heard about this issue before. Some blogs suggest a quick workaround which is place a Start-Sleep command in directly after the Setup Windows and ConfigMgr step. This allows the client to fully initialize and work as expected.

Have you tried this earlier ?.

Powershell.exe -ExecutionPolicy Bypass -Command “Start-Sleep -s 120”

Thanks [B]Desai[/B] i will try,
btw do you have any tool or software can collect all drives or software in-compatibility with win 10 before we upgrade ?

 

[bom2010]

Already ran powershell as below. However it's not working
Powershell.exe -ExecutionPolicy Bypass -Command “Start-Sleep -s 120”
Anyone have solution help me

 

[mchippy]

I'm facing this issue with a client on some HP models. Oddly enough, they found this issue doesn't happen when deploying 21H2 with the 21H2 drivers from HP. Only when deploying 22H2 with the 22H2 drivers. And it's also not terribly consistent, which makes it harder to diagnose. Still scratching my head over it.

 

[trashscientist]

I've started experiencing this issue after upgrading Configuration Manager to 2409. Has anyone discovered a fix or workaround?