You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am on the latest version of Atlas, and didn't do an unsupported upgrade
Description
After atlas os was installed and rebooted, veracrypt encryption was started, and after the encryption was completed, it repeatedly appeared to be stuck on a black screen when rebooting or shutting down the computer.
Steps to reproduce
1.Installation of the system using the official windows 11 23h2 image
2.Full installation tutorial install atlas os and reboot
3.Follow the veracrypt software's wizard to encrypt your system.
The bug is also reproducible on atlas os 10, which also appears to be stuck for a while during system operation, and the encryption works fine on systems with only a normal installation and no atlas os installed, presumably because some optimization measures are corrupting the prerequisites for the veracrypt encryption driver to work.
Sometimes the bug will not appear.
The text was updated successfully, but these errors were encountered:
Before continuing...
Description
After atlas os was installed and rebooted, veracrypt encryption was started, and after the encryption was completed, it repeatedly appeared to be stuck on a black screen when rebooting or shutting down the computer.
Steps to reproduce
1.Installation of the system using the official windows 11 23h2 image
2.Full installation tutorial install atlas os and reboot
3.Follow the veracrypt software's wizard to encrypt your system.
Expected behavior
Normal reboot and shutdown
Actual behavior
Stuck on a black screen during reboot
Atlas Edition
Atlas for Windows 11 23H2
Desktop information
Additional content
The bug is also reproducible on atlas os 10, which also appears to be stuck for a while during system operation, and the encryption works fine on systems with only a normal installation and no atlas os installed, presumably because some optimization measures are corrupting the prerequisites for the veracrypt encryption driver to work.
Sometimes the bug will not appear.
The text was updated successfully, but these errors were encountered: