### Tested versions

- Reproducible: all godot 4 versions - Godot_v4.2-stable_win64 (last version I tested)
- Not reproducible: before godot 4 versions - I'm currently working on Godot_v3.5.3-stable_win64, and there is no issue

### System information

Godot v4.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated AMD Radeon (TM) R5 M330 () - AMD A8-7410 APU with AMD Radeon R5 Graphics (4 Threads)

### Issue description

The bug appears as soon as I start godot, all the interface is not properly shown, when I move over any option on the interface with the mouse the interface start to blink and the options are not shown, and I've already tested other godot 4 versions and the problem persist, only on the godot 3 versions the problem is not happening.

### Steps to reproduce

There are not steps, the problem can be noticed on the interface where we create a new project or select an exiting one, any clickeable option triggers this problem.

### Minimal reproduction project (MRP)

https://youtu.be/VTGknO_ML-o

_Production edit: updated the system info_
#ifdef TESTS_ENABLED
	for (int x = 0; x < argc; x++) {
		if ((strncmp(argv[x], "--test", 6) == 0) && (strlen(argv[x]) == 6)) {
			tests_need_run = true;
			
			
			test_setup();
			int status = test_main(argc, argv);
			test_cleanup();
			return status;
		}
	}
#endif
	tests_need_run = false;
	return 0;
}
/* Engine initialization
 *
 * Consists of several methods that are called by each platform's specific main(argc, argv).
 * To fully understand engine init, one should therefore start from the platform's main and
 * see how it calls into the Main class' methods.
 *
 * The initialization is typically done in 3 steps (with the setup2 step triggered either
 * automatically by setup, or manually in the platform's main).
 *
 * - setup(execpath, argc, argv, p_second_phase) is the main entry point for all platforms,
 *   responsible for the initialization of all low level singletons and core types, and parsing
 *   command line arguments to configure things accordingly.
 *   If p_second_phase is true, it will chain into setup2() (default behavior). This is
 *   disabled on some platforms (Android, iOS) which trigger the second step in their own time.