Turns out, I needed an older build of VMware Tools (not VMware Workstation), once downgraded, Aero works perfectly and all visual glitches are gone. and I think I should run away because that blob that's sobbing is slowly haunting me.
Windows Vista works fine on Workstation 17, it was because the VMware Tools installed on Vista caused conflicts with Workstation 17. I since then downgraded VMware Tools and the issues were eliminated.
Thing possibly happened: I think the version you're on windows 10 is outdated and so the programs aren't compatible with the version, so the thing is, VMWare 17 just has problems emulating an Os and the ui itself on it's version of windows, Simplified version here: -The version you're running has a little different code than newer ones. -VMWare has 22H2 designed code -Your version is not compatible -VMWare tries to emulate anyways, and has horrible problems with it due to the incompatible version you're using.
It's interesting, since I do have a Windows 11 partition that I use rarely, and I booted the VM up on there, which has the same result. It turns out to be the VMware Tools installed on Vista conflicting with Workstation 17. I downgraded VMware Tools and all issues were fixed, so it's not an old OS issue, but a problem with Workstation 17.
I chose to install LTSB 2016 specifically because it's far more stable than newer Windows 10/11 builds out there, while I understand I don't get the "new and fancy" features, almost everything I do on that build of Windows 10, released back in 2016 continues to work flawlessly. I don't find the need to upgrade every year/two years for some "new" features I don't end up using with more and more builds becoming unstable, and I have security updates up until 2026.
There are many reasons why I have chosen 1607, not only it's more stable than those newer builds, I can get everything done on that build without needing to upgrade every year or so.
@@TechnologicalByte I have a computer from 2013 (my main driver, a Samsung AIO) and the latest driver is for 1607, past that the Bluetooth doesn’t work. Otherwise it runs Windows 11 well. I enjoy stability but with the amount of personal and sensitive information for multiple hundreds of people that runs through it, I worry a ton about security.
@@TechnologicalByte The stability issues are likely due to using Nvidia. I'm using only Intel and have no issues. Version 20H2 onwards are enablement packages for version 2004 and there's no real need to clean install between these versions, only clean install if you're running version 1909 or earlier.
Turns out, I needed an older build of VMware Tools (not VMware Workstation), once downgraded, Aero works perfectly and all visual glitches are gone.
and I think I should run away because that blob that's sobbing is slowly haunting me.
can i have it
5:22 honestly this part looked cooler than the original
VirtualBox, literally VirtualBox 7 on every existing OS and every existing version of every existing OS:
Finally, a worthy opponent.
Good video, I subscribed
When You forgot to update Your GPU drivers in 2 Years:
LOL TRUE
The real reason it's buggy is that Windows Vista and below have issues in 17. This also happened to Come on Windows.
Windows Vista works fine on Workstation 17, it was because the VMware Tools installed on Vista caused conflicts with Workstation 17. I since then downgraded VMware Tools and the issues were eliminated.
@@TechnologicalByte Hello, How did you create the intro for your short how to break windows 10. please tell me
That short I did was created in Adobe Premiere, including the intro.
literally virtualbox 7.0 graphical glitches amplified to 9000
VBox does not work with 3D acceleration aero effects
(edit: it works in 4.0.xx to 5.2.xx)
5:15 Me when i use my pc:
The ultimate softwaregore.
Windows Media Player has stopped.
Thing possibly happened:
I think the version you're on windows 10 is outdated and so the programs aren't compatible with the version, so the thing is, VMWare 17 just has problems emulating an Os and the ui itself on it's version of windows,
Simplified version here:
-The version you're running has a little different code than newer ones.
-VMWare has 22H2 designed code
-Your version is not compatible
-VMWare tries to emulate anyways, and has horrible problems with it due to the incompatible version you're using.
It's interesting, since I do have a Windows 11 partition that I use rarely, and I booted the VM up on there, which has the same result. It turns out to be the VMware Tools installed on Vista conflicting with Workstation 17. I downgraded VMware Tools and all issues were fixed, so it's not an old OS issue, but a problem with Workstation 17.
Alright i guess i was wrong then, by the way i enjoyed the video
i have 22h2 (11) and its slow and bios is just black
0:27
U can enable dark mode with winaero tweaker
(it has it)
i think vmware tools isn't compatible
Yeah, turns out the one installed on Vista caused conflicts with Workstation 17; I since then downgraded Tools and the issues are gone.
@@TechnologicalByte This happens if you try to run a incompatible version of VMware Tools.
Some other people had also problems on 17 version with vista idk why
Ist Windows Vista Okay for you?
Why do you use an LTSC release of Windows 10?
I chose to install LTSB 2016 specifically because it's far more stable than newer Windows 10/11 builds out there, while I understand I don't get the "new and fancy" features, almost everything I do on that build of Windows 10, released back in 2016 continues to work flawlessly. I don't find the need to upgrade every year/two years for some "new" features I don't end up using with more and more builds becoming unstable, and I have security updates up until 2026.
@@TechnologicalByteI have 22H2. :D
6:00
8:59
Why run 1607 as your main OS?
There are many reasons why I have chosen 1607, not only it's more stable than those newer builds, I can get everything done on that build without needing to upgrade every year or so.
@@TechnologicalByte I have a computer from 2013 (my main driver, a Samsung AIO) and the latest driver is for 1607, past that the Bluetooth doesn’t work. Otherwise it runs Windows 11 well. I enjoy stability but with the amount of personal and sensitive information for multiple hundreds of people that runs through it, I worry a ton about security.
@@TechnologicalByte The stability issues are likely due to using Nvidia. I'm using only Intel and have no issues. Version 20H2 onwards are enablement packages for version 2004 and there's no real need to clean install between these versions, only clean install if you're running version 1909 or earlier.
*Promo sm* 😢