Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
Also I personally think the crash behavior is inconstant for different PCs, that's probably why people's reports are varied, hence more difficult to address this issues.
I have 3 PC and they all react differently: 1 desktop which won't crash unless click the Copilot, while another desktop and laptop will just crash instantly when the Windows start up even without click the Copilot. All my PCs were running Wallpaper Engine completely fine before this Windows update.
Pretty sure there are more than that which caused the issues (besides the Copilot itself).
Could you switch to the latest Wallpaper Engine 2.3 beta, then reproduce the issue on your system and check if there are any new .mdmp files in the wallpaper_engine directory? Check the date and time on the .mdmp files, they should really be "brand new files" just right after the crash on your system.
Since you are using multiple computers, it would be super important that you clearly explain which computer the specific .mdmp file would be from so that we can differentiate these issues. A log file of the computer from our analysis tool would also be important:
https://help.wallpaperengine.io/en/debug/scantool_support.html
You can email it all to our support email with some clear title (like your user name and that it's about the copilot crashes or whatever) so that I can find your email. We'll take a look but the issue remains that we cannot reproduce this problem, also because Microsoft seems to be rolling out these changes slowly across the Windows user base and we simply don't have all the options available as of right now.
Thanks for your reply,I switch to the latest Wallpaper Engine 2.3 beta,and turn on the full log mode,When I see the log file,I think is not crash,look like the windows is changed when Copilot was start and Wallpaper Engine is detected it.
About Copilot preview,you can join the windows insider program,and select the beta channel.You can used the VMWare to preview it,and the problem can then be reproduced quite simply.
https://www.windowscentral.com/software-apps/windows-11/microsoft-copilot-caused-some-pcs-to-crash-but-theres-already-a-fix