# Grok Bot shared computer stuck "still starting up" for 9+ hours — no Update/Recover option, need server-side recovery

**URL:** <https://forum.cursor.com/t/grok-bot-shared-computer-stuck-still-starting-up-for-9-hours-no-update-recover-option-need-server-side-recovery/177993>\
**Category:** Bug Reports\
**Tags:** grok-bot\
**Created:** [November 10, 2026, 7:05pm UTC](https://forum.cursor.com/t/grok-bot-shared-computer-stuck-still-starting-up-for-9-hours-no-update-recover-option-need-server-side-recovery/177993 "2026-11-10T19:05:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![iwaishin](https://avatars.discourse-cdn.com/v4/letter/i/d6d6ee/32.png) [@iwaishin](https://forum.cursor.com/u/iwaishin)\
**Post date:** [November 10, 2026, 7:05pm UTC](https://forum.cursor.com/t/grok-bot-shared-computer-stuck-still-starting-up-for-9-hours-no-update-recover-option-need-server-side-recovery/177993/1 "2026-11-10T19:05:39Z")

</div>

### Where does the bug appear (feature/product)?

Grok Bot

### Describe the Bug

Since about 18:30 Asia/Tokyo on Nov 10, 2026, Grok Bot’s shared computer has been stuck. Bots still reply in chat, but every Shell / Read / Screenshot call returns “The computer is still starting up. Try again in a moment.” It has stayed this way for over 9 hours.

Settings \> Computer only shows Reset. There is no “Update Bot’s Computer” or “Recover computer” button. Support (by email) advised NOT to Reset yet, and a scheduled backup on the box failed because the computer was unreachable, so a Reset would likely lose recent unsynced work.

### Steps to Reproduce

1. Open Grok Bot on Windows (desktop app 0.79.3), signed in.
2. Ask any bot to run a simple command (e.g. echo ok) or read a file.
3. It always returns “still starting up”; nothing runs.
4. Fully quit and reopen the app, check for app updates: no change.
5. Open Settings \> Computer: only Reset is offered, no Update or Recover.

### Expected Behavior

Please clear the stuck state / rebuild the computer from the backend while keeping bots, chats, files, and logins. I will not Reset from the client unless engineering asks me to.

### Operating System

Windows 10/11  
iOS

### Version Information

Grok Bot 0.79.3 (Windows desktop app)

### For AI issues: which model did you use?

N/A — computer stuck starting up, not a model reply issue

### Additional Information

Support ticket already opened by email: T-J77937. Bots, chats, files and logins must be kept — please do not ask for more Reset from the client.

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [November 11, 2026, 2:35pm UTC](https://forum.cursor.com/t/grok-bot-shared-computer-stuck-still-starting-up-for-9-hours-no-update-recover-option-need-server-side-recovery/177993/8 "2026-11-11T14:35:08Z")

</div>

Hi @iwaishin, your computer should be working again! Can you check?

---

<div class="post-metadata">

**Author:** ![iwaishin](https://avatars.discourse-cdn.com/v4/letter/i/d6d6ee/32.png) [@iwaishin](https://forum.cursor.com/u/iwaishin)\
**Post date:** [November 12, 2026, 6:21am UTC](https://forum.cursor.com/t/grok-bot-shared-computer-stuck-still-starting-up-for-9-hours-no-update-recover-option-need-server-side-recovery/177993/10 "2026-11-12T06:21:18Z")

</div>

The system is back up and running. Thanks so much for your help!

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [November 14, 2026, 6:21am UTC](https://forum.cursor.com/t/grok-bot-shared-computer-stuck-still-starting-up-for-9-hours-no-update-recover-option-need-server-side-recovery/177993/11 "2026-11-14T06:21:27Z")

</div>

Closed on November 14, 2026, 6:21am UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
