| Forum Home | ||||
| PC World Chat | ||||
| Thread ID: 138792 | 2015-01-24 04:33:00 | Windows 11 Latest Tech Preview | wainuitech (129) | PC World Chat |
| Post ID | Timestamp | Content | User | ||
| 1392815 | 2015-03-31 06:27:00 | Also "If you have Virtual Machines hosted on your PC running Windows 10, you will want to move to the Slow ring and wait for the next build as this build breaks the ability to run VMs". That could impact some people here I think. That sounds like a challenge if I ever heard one LOL :lol::lol: |
wainuitech (129) | ||
| 1392816 | 2015-03-31 06:42:00 | How much do I win if I can get it working on a VM ?:D | wainuitech (129) | ||
| 1392817 | 2015-03-31 08:02:00 | How much do I win if I can get it working on a VM ?:DIf anyone could, I bet it would be you. :). When I reread item, I think what it actually means is that you can't run a VM under this build. | Tony (4941) | ||
| 1392818 | 2015-03-31 08:07:00 | How much do I win if I can get it working on a VM ?:D A bag of lollies and a balloon, 2nd person to get it working gets two copies of W8xx, 3rd person gets 4 copies, 4th person gets W10. ;) |
R2x1 (4628) | ||
| 1392819 | 2015-03-31 08:31:00 | If anyone could, I bet it would be you. :). When I reread item, I think what it actually means is that you can't run a VM under this build. Welllllllllllll if they reckon it wont run in VM, then errrrrrrrrrrrrrrrrrrrrrrr Wrong !!! If they mean you cant run a VM in 10049 -- I'll test that theory later. Proof of course in Pictures - Other wise didn't happen --> Base OS is Windows 7, running Windows 10 10049 in a VMware Workstation. 633263336334 Had to change the default desktop Pic other wise the build number was to hard to see. Edited, just found this -- Looks like 10094 wont run Hyper-V. Another deal-breaker would be if you're using Windows 10 as a host for Hyper-V virtual machines, because Build 10049 also breaks the ability to boot VMs, too. Seems the reports are a little bit confusing. |
wainuitech (129) | ||
| 1392820 | 2015-03-31 08:44:00 | If they mean you cant run a VM in 10049 -- I'll test that theory later.That's how I read the item when I looked at it a second time. | Tony (4941) | ||
| 1392821 | 2015-03-31 09:28:00 | This is how I read it too. I wouldn't be surprised if you can't run Hyper-V if your W10 install is Virtual anyway. Pretty sure you can't run a hypervisor in a hypervisor. Or maybe you can but not use Hardware VT. | Alex B (15479) | ||
| 1392822 | 2015-03-31 21:44:00 | OPPPPPPSSS :lol::lol: Maybe the reports should actaully investigate before reporting, either that or I've just done the impossible :nerd: May not work in Hyper-V on W10 10049 BUT picture says it all. Windows 10 -- 10049 ( host OS) + VMWare Player running Windows 7. 6336 |
wainuitech (129) | ||
| 1392823 | 2015-04-01 00:05:00 | OPPPPPPSSS :lol::lol: Maybe the reports should actaully investigate before reporting, either that or I've just done the impossible :nerd: May not work in Hyper-V on W10 10049 BUT picture says it all. Windows 10 -- 10049 ( host OS) + VMWare Player running Windows 7. That's really interesting. My original quote was from "known probs in this build" from the windows insider app. |
Tony (4941) | ||
| 1392824 | 2015-04-01 02:57:00 | That's really interesting. My original quote was from "known probs in this build" from the windows insider app. uit was more than likely referring to Winodws own hyper-V. (but it didn't say that in many places) I uninstalled VM Player, and loaded in Hyper-V from Programs and features, it created the hyper-V OK, but when trying to make a VM it spat the dummy -- something about not being able to create due to problems with shared access (or something like that) |
wainuitech (129) | ||
| 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 | |||||