RE: vmware fusion 7 and windows 7 becoming unactive
Hi. As I recall, there are two different ways to run a bootcamp partition in Fusion. The first imports the machine, and considers it a new machine. The second simply runs the bootcamp partition in Fusion, and does not require reactivation. I remember having this problem, but I can no longer find what each of these items are labeled as since I no longer have a bootcamp partition. -Original Message- From: macvisionaries@googlegroups.com [mailto:macvisionaries@googlegroups.com] On Behalf Of Juan Hernandez Sent: Monday, March 30, 2015 3:09 AM To: macvisionaries@googlegroups.com Subject: Re: vmware fusion 7 and windows 7 becoming unactive Hello, Thanks for letting me know this. That make sense if I am importing the bootcamp into a vm disk file. But I am actually accessing the bootcamp partition directly. I will look into making windows 7 recognize the vm environment as the real one. Thanks for the input, I really appreciate it. Best, Juan Hernandez Email: juanhernande...@gmail.com Cell: 619-750-9431 Follow me at: http://www.twitter.com/blindwiz friend me at: http://www.facebook.com/blindwiz Web site: http://www.juanhernandez.me On Mar 26, 2015, at 7:19 PM, Phil Halton philh...@gmail.com wrote: I remember something like this happening to me a long time ago. I believe it happens because when you access the windows bootcamp installation via fusion, it is as though you are running windows, and everything in it, on a new computer. The fusion virtual environment is essentially a simulated piece of hardware and windows thinks it is being run on a different piece of hardware than it was authorized for. The same goes for Jaws, Office, and all other programs that are tied to the hardware for licensing purposes. Having said all that, I don’t remember the fix, but I believe there is one. Otherwise you’d have to reauthorize everything for use in fusion. It might be in the way you access the bootcamp. There is some setting to be checked or unchecked when you import the bootcamp into fusion. I know that when you import a VM file into fusion from another machine, you have to be careful to “move” and not “copy” the vm, otherwise fusion won’t import the license along with the vm file. and you’ll have to reauthorize everything because when you do a copy, you’re essentially “creating a new copy of windows that requires authorization. Something like that may be happening when you import the bootcamp into fusion. In fact, I’d bet on it. You may want to try deleting the bootcamp VM, (not bootcamp itself, just the imported VM), and reimport the bootcamp partition and watch for this sort of thing. On Mar 26, 2015, at 8:22 PM, Juan Hernandez juanhernande...@gmail.com wrote: Hi All, I have a weird question. My configuration is, macbook pro w/ mac os x 10.10.2, and windows 7 installed in a bootcamp partition. Now, I have VMWare Fusion installed so I can access the bootcamp partition via fusion when booted into the mac. When ever I start the bootcamp machine, it makes my windows 7 installation unactivated. Windows update, and the windows activation keep coming up. When I boot into windows 7 directly, outside of mac os x, it is working perfectly. Have any of you guys incountered this? Any help would truly be appreciated. This is rather annoying. Best, Juan -- You received this message because you are subscribed to the Google Groups MacVisionaries group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups MacVisionaries group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups MacVisionaries group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups MacVisionaries group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries
Re: vmware fusion 7 and windows 7 becoming unactive
Hello, Thanks for letting me know this. That make sense if I am importing the bootcamp into a vm disk file. But I am actually accessing the bootcamp partition directly. I will look into making windows 7 recognize the vm environment as the real one. Thanks for the input, I really appreciate it. Best, Juan Hernandez Email: juanhernande...@gmail.com Cell: 619-750-9431 Follow me at: http://www.twitter.com/blindwiz friend me at: http://www.facebook.com/blindwiz Web site: http://www.juanhernandez.me On Mar 26, 2015, at 7:19 PM, Phil Halton philh...@gmail.com wrote: I remember something like this happening to me a long time ago. I believe it happens because when you access the windows bootcamp installation via fusion, it is as though you are running windows, and everything in it, on a new computer. The fusion virtual environment is essentially a simulated piece of hardware and windows thinks it is being run on a different piece of hardware than it was authorized for. The same goes for Jaws, Office, and all other programs that are tied to the hardware for licensing purposes. Having said all that, I don’t remember the fix, but I believe there is one. Otherwise you’d have to reauthorize everything for use in fusion. It might be in the way you access the bootcamp. There is some setting to be checked or unchecked when you import the bootcamp into fusion. I know that when you import a VM file into fusion from another machine, you have to be careful to “move” and not “copy” the vm, otherwise fusion won’t import the license along with the vm file. and you’ll have to reauthorize everything because when you do a copy, you’re essentially “creating a new copy of windows that requires authorization. Something like that may be happening when you import the bootcamp into fusion. In fact, I’d bet on it. You may want to try deleting the bootcamp VM, (not bootcamp itself, just the imported VM), and reimport the bootcamp partition and watch for this sort of thing. On Mar 26, 2015, at 8:22 PM, Juan Hernandez juanhernande...@gmail.com wrote: Hi All, I have a weird question. My configuration is, macbook pro w/ mac os x 10.10.2, and windows 7 installed in a bootcamp partition. Now, I have VMWare Fusion installed so I can access the bootcamp partition via fusion when booted into the mac. When ever I start the bootcamp machine, it makes my windows 7 installation unactivated. Windows update, and the windows activation keep coming up. When I boot into windows 7 directly, outside of mac os x, it is working perfectly. Have any of you guys incountered this? Any help would truly be appreciated. This is rather annoying. Best, Juan -- You received this message because you are subscribed to the Google Groups MacVisionaries group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups MacVisionaries group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups MacVisionaries group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout.
Re: vmware fusion 7 and windows 7 becoming unactive
I remember something like this happening to me a long time ago. I believe it happens because when you access the windows bootcamp installation via fusion, it is as though you are running windows, and everything in it, on a new computer. The fusion virtual environment is essentially a simulated piece of hardware and windows thinks it is being run on a different piece of hardware than it was authorized for. The same goes for Jaws, Office, and all other programs that are tied to the hardware for licensing purposes. Having said all that, I don’t remember the fix, but I believe there is one. Otherwise you’d have to reauthorize everything for use in fusion. It might be in the way you access the bootcamp. There is some setting to be checked or unchecked when you import the bootcamp into fusion. I know that when you import a VM file into fusion from another machine, you have to be careful to “move” and not “copy” the vm, otherwise fusion won’t import the license along with the vm file. and you’ll have to reauthorize everything because when you do a copy, you’re essentially “creating a new copy of windows that requires authorization. Something like that may be happening when you import the bootcamp into fusion. In fact, I’d bet on it. You may want to try deleting the bootcamp VM, (not bootcamp itself, just the imported VM), and reimport the bootcamp partition and watch for this sort of thing. On Mar 26, 2015, at 8:22 PM, Juan Hernandez juanhernande...@gmail.com wrote: Hi All, I have a weird question. My configuration is, macbook pro w/ mac os x 10.10.2, and windows 7 installed in a bootcamp partition. Now, I have VMWare Fusion installed so I can access the bootcamp partition via fusion when booted into the mac. When ever I start the bootcamp machine, it makes my windows 7 installation unactivated. Windows update, and the windows activation keep coming up. When I boot into windows 7 directly, outside of mac os x, it is working perfectly. Have any of you guys incountered this? Any help would truly be appreciated. This is rather annoying. Best, Juan -- You received this message because you are subscribed to the Google Groups MacVisionaries group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups MacVisionaries group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout.
