This message was deleted.

Auto-updates for 1.13.1 has been enabled.

I'm not being offered the update - anything i need to do? (Windows)

Don't think so, other than making sure the checkbox for updates is checked. (I actually tested that I could do an update on Windows before sending that message… but that was a new VM, so it had never checked before.) Note that we rate-limit our update checks, so you may have to wait a bit before it checks again (but it should have elapsed by now).

I've had the app open all day

In that case, if you want to dig into it you can consider looking at

update.log

in the logs directory to see if that says anything; turning on the debug mode setting there and restarting Rancher Desktop would also provide more verbose logs.

2024-03-18T160244.380Z: Checking for update 2024-03-18T160246.338Z: Update for version 1.12.3 is not available (latest version: v1.12.3, downgrade is disallowed). 2024-03-18T170245.546Z: Checking for update 2024-03-18T170247.665Z: Update for version 1.12.3 is not available (latest version: v1.12.3, downgrade is disallowed). 2024-03-18T180246.599Z: Checking for update 2024-03-25T081305.022Z: Error: FetchError: request to https://api.github.com/repos/rancher-sandbox/rancher-desktop/releases/tags/v1.12.3 failed, reason: read ECONNRESET at ClientRequest.<anonymous> (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\node-fetch\lib\index.js150111) at ClientRequest.emit (nodeevents513:28) at TLSSocket.socketErrorListener (node http client502:9) at TLSSocket.emit (nodeevents513:28) at emitErrorNT (nodeinternal/streams/destroy151:8) at emitErrorCloseNT (nodeinternal/streams/destroy116:3) at process.processTicksAndRejections (nodeinternal/process/task queues82:21)

Hmm, so it's not seeing the update to 1.13.1 at all (and it's failing to fetch 1.12.3; I'm more confused that it's even trying, since you already have it…)

i'll try a full reboot

And I need to try a 1.12.2 → 1.13.1 upgrade for another issue anyway, so I'll be doing the upgrade check again at the same time

Its working following system reboot