In any case, I wanted to post this in case someone else ended up with this same problem. The expanding of physical memory to 16 gigs from 8 gigs forced the system to reconfigure the 'virtual' memory or swap space and then when I shrank the physical memory back to 8 gigs from 16 gigs, the swap or virtual memory settings remained where they were. So for some reason, expanding and contracting the physical memory seems to have made the problem go away.īecause of this, I think the underlying problem was that I didn't have enough 'virtual' memory or swap space configured on the guest Windows 7 OS. I booted up and the error message didn't come back. The windows of open programs and the bottom toolbar changed to the classic mode. I then shut the system down, and shrank the physical memory back to 8 gigs. Windows 7 Theme Stuck in Classic Mode My computer automatically installed a windows update and when my computer restarted I immediately noticed some changes. I booted up the Windows 7 OS and the error went away. I have two UHD displays and an initial physical memory configured at 8 gigs.Īfter messing around a bit with the display settings under the Windows 7 guest OS, I stumbled across an odd solution to the problem.įirst I expanded the guest physical memory from 8 gigs to 16 gigs.

It would then turn off the Areo display stuff. When I logged in, with the vm configured with 3D display setting enabled and 2 gigs of shared memory, the OS would spit out a message saying there wasn't enough resources for the current display setting and that it reverted the display settings back to a basic setting. I just spent a bunch of time with an odd problem when I upgraded from vmware workstation 10 to 11 on a fedora 20 linux hosts running a windows 7 guest OS.

Windows 7 stuck in basic color scheme