Answer
This error pattern strongly suggests one or more of the required Windows services supporting IFS (MWS and related components) simply didn't come back up after the VM restart — confirm all the required IFS Windows services are actually running first. If there's no single all-in-one startup script available for that specific demo package, use mws-svr.cmd in the instance's bin directory to issue a START command for all servers, which starts everything in the correct dependency order. Once the core servers are confirmed running this way, you should regain access to both the application and the Admin Console (some optional demo-specific services, like CBS or Demand Planner, may need separate attention beyond this).