-
I just noticed that the upgrade changed my local (former Win10-)daily user account into a “WDAGUtilityAccount”, which is no longer determined as a “User” but as a “Guest”.
1 user thanked author for this post.
-
No third party clock app. I read several complaints about it online.
1 user thanked author for this post.
-
Start11, but it turns out that (at least on 24H2) that program only gives the choice for the taskbar to be on the top or bottom of the screen – not the left or right. (I am now trying to get a refund for it).
Taskbar choices for left and right are available in the beta. You can download the beta within your Start11 account.
You were/are right @PL1
It was not immediately clear where and how to get the Beta, but once I created an account on Stardock I was indeed able to download and install it.
I now have my preferred right side taskbar and square window corners. Thanks a lot
Hopefully this Beta gets developed into a stable version and that a future Windows update doesn’t mess it up
1 user thanked author for this post.
-
-
-
I’ll have a peek at that beta.
@PL1 I answered your question below already 3 or 4 times, but my answers don’t show up in the topic. So I try it this way.I disabled the Recommended in all settings in both accounts.
Moderator’s Note: Retrieved from the spam bucket, also removed extraneous HTML.
1 user thanked author for this post.
-
-
-
-
-
-
-
Although I use my system both for work and play, I consider myself a consumer when it comes to updates.
However, given the precarious situation, I decided to install Windows 10 22H2 KB5041580 – after making a backup.All went well, but after I rebooted a second time my dual boot Windows-Mint pc wouldn’t start (no Grub boot menu) and I got the error message
“Verifying shim SBAT data failed: Security Policy Violation.
Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation” and the pc shut down.Luckely the web provided the solution: https://forums.linuxmint.com/viewtopic.php?p=2510718&sid=b052f39ccc46129bed219c179178a4b2#p2510718
Steps to solve the problem:
1. Disable Secure Boot
2. Log into your Ubuntu (Mint) user and open a terminal
3. Delete the SBAT policy with:
sudo mokutil –set-sbat-policy delete *
4. Reboot your PC and log back into Ubuntu (Mint) to update the SBAT policy:
sudo mokutil –set-sbat-policy latest *
5. Reboot and then re-enable secure boot in your BIOS.*Please beware: on my pc the font makes the command look like there’s only 1 hiphen before “set”, but there are/should be 2 hiphens in front of “set”.
Don’t ask me why, but the solution worked. All is well now
-
-
Author
