UNFORTUNATELY, this whole thing is NOT a good solution for anyone (like me) who already has MANY TERABYTES of existing VMWare image files: You'll need to spend a huge amount of time CONVERTING those into. NOTE: You can download the conversion program (OVFTool.exe) by itself from VMWare here:īecause if you allow the Windows 10 update to DELETE VMWare install, it will delete this too! Here are SOME VERY IMPORTANT CAVEATS CONCERNING switching from VMWare to VirtualBox: But it's your software telling me I can no longer use an application that runs just fine under Win 10 1809. though I certainly find them at fault in this as well. You are effectively telling me I must get new hardware or never be able to update Windows 10! (And don't blame VMWare. and of course a new CPU and then new Memory which is currently DDR2 not DDR3.)ĭOES MICROSOFT HAVE AN UPDATE THAT WILL ALLOW ME TO CONTINUE USING VMWare 12.5 ? it can't work with any CPU beyond what I already have!. because I cannot afford to purchase a whole new PC! (I would need a completely new motherboard. both have same issue:), it said it could not function with my INTEL Q6600 CPU !!! I had to go back to Win 10 version 1809. But when I tried to install the new VMWare version (it was a 14 or 15. Upon upgrading to Windows 10 version 1903 (or later I would assume!), the update told me I could no longer use VMWare 12.5 (but that VMWare would supply a later version I could use. Please message the moderators and we'll pull it back in.My platform has an Intel Q6600 (Dual Core Quad) CPU. If you make a post and then can't find it, it might have been snatched away. The spam filter can get a bit ahead of itself. To get flair with your certification level send a picture of your certificate with your Reddit username in the picture to the moderators. If you are an employee, please PM one of the moderators that has a VMware logo for verification instructions and we will add it to yours as well! The VMware logo icon following a username indicates that this user is a VMware employee. Specify your problems/needs, technical requirements, and objectives clearly. When asking for assistance or advice, please give the community sufficient information to work with. When asking for technical support, please specify the specific VMware product(s) and version(s) you are working with. While discussion of virtualization concepts in general is appropriate, requesting technical help for non-VMware products is off-topic. Posts that fail to meet these guidelines may be locked or removed: Vulgarity and hostility towards other users will not be tolerated.ĭon't post brain dumps for certification exams. Want to promote something within the community? Message the mods first with your proposal, and we'll decide if it's too spammy or not.ĭon't be a jerk. Brazen marketing material is also generally unwelcome. within a short period of time will be considered spam. Repeatedly submitting links to the same blog/YouTube channel/etc. Don't submit links to blogspam or other low-quality content. Spammers will be banned this sub will not become a marketing cesspit for vendors. Off-topic posts may be locked or removed. Keep post submissions relevant to VMware. Support requests involving Mac OS on unsupported hardware (not a Mac) or software (VMware Workstation or VMware Player) will be removed, and will result in a ban. This includes discussion of 'unlocker' or other methods used to violate the Mac OS EULA by running Mac OS on non-Apple hardware. Expect posts facilitating or promoting piracy to be removed. Have a technical question? Just make a self post!ĭiscussion of piracy methods will not be permitted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |