Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm
Đã giải quyết

Upgrade from 155.0 to 155.0.1 was unstable, reverted

Forrest

I updated to 155.0.1 via the update modal yesterday, on MacOS Tahoe, and it didn't restart as normal. The main message pane was blank with "No Message Found" (screenshot attached).

I tried installing a fresh 155.0 over, that did not work; but, a restore of the prior app from my Time Machine did work -- that is, the application not the user profile data.

I just thought this was strange; never ran into it.

If there is an issue and I can help test it usefully, I happy to do so (I have backups! LOL).


Forrest

I updated to 155.0.1 via the update modal yesterday, on MacOS Tahoe, and it didn't restart as normal. The main message pane was blank with "No Message Found" (screenshot attached). I tried installing a fresh 155.0 over, that did not work; but, a restore of the prior app from my Time Machine did work -- that is, the application not the user profile data. I just thought this was strange; never ran into it. If there is an issue and I can help test it usefully, I happy to do so (I have backups! LOL). Forrest
Đính kèm ảnh chụp màn hình
Đọc câu trả lời này trong ngữ cảnh

Giải pháp được chọn

So, there was a quick update to 156.0, which I performed and the problem has resolved.

So, I have no idea what the issue was. But it's fixex, for me, for now.

Tất cả các câu trả lời (3)

So you are back on version 154.0?

No, I downgraded from 155.0.1 to 155.0 and things were stable again. I'm not entirely sure what happened -- I'm willing to 'try again' as I do have backups, but I wanted to put this info out there in case I ran into something that needs more info.

Giải pháp được chọn

So, there was a quick update to 156.0, which I performed and the problem has resolved.

So, I have no idea what the issue was. But it's fixex, for me, for now.

Đặt một câu hỏi

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.