VMware workstation windows host shared folders issue
My laptop is a Linux mint powered host and a windows 8 guest via VMware Workstation.
Yesterday, I get the bad and stupid idea to upgrade my windows 8 to windows 8.1 final release, using the Installer from the ISO.
After everything installed, I logged into my guest windows 8.1, and surprise, I can't map
VMWare Shared Folders as network drive, or simply see, as I could before, "vmware-host" in the list of network locations.
I supposed it could be an issue related to the "TrustedInstaller" user folders ownership, so I tried to update the ownership of system files to the "Administrators" group, but nothing changed.
Anyone has an idea of what can I do, before totally deleting my VM and start again with a new one from scratch?
Thanks in advance
windows-8 security virtualization vmware-workstation
asked Sep 20 '13 at 21:57
Hoghweed
12113
add a comment |
My laptop is a Linux mint powered host and a windows 8 guest via VMware Workstation.
Yesterday, I get the bad and stupid idea to upgrade my windows 8 to windows 8.1 final release, using the Installer from the ISO.
After everything installed, I logged into my guest windows 8.1, and surprise, I can't map
VMWare Shared Folders as network drive, or simply see, as I could before, "vmware-host" in the list of network locations.
I supposed it could be an issue related to the "TrustedInstaller" user folders ownership, so I tried to update the ownership of system files to the "Administrators" group, but nothing changed.
Anyone has an idea of what can I do, before totally deleting my VM and start again with a new one from scratch?
Thanks in advance
windows-8 security virtualization vmware-workstation
asked Sep 20 '13 at 21:57
Hoghweed
12113
What version of Vmware Workstation? They just released v10 which offers Windows 8.1 support. The Vmware tools probably get updated, and the Guest drivers.
– Zoredache
Sep 20 '13 at 22:42
I'm using vmware 10, I know a clean vm windows 8.1 works as a sugar, but my problem has begun after I updated my guest windows 8 to windows 8.1 using the installer
– Hoghweed
Sep 21 '13 at 0:00
After installing the VMWare tools you can shutdown the VM, edit the .VMX file replacing all occurances of "e1000e" with "vmxnet3" then see if things improve. This switches from an emulated Intel network card to a VMware paravirtualized NIC.
– Brian
Sep 21 '13 at 4:11
reinstall the vmware tools in the VM.
– magicandre1981
Sep 21 '13 at 5:40
@magicandre1981 I've done three times but nothing changed.. I saw, while googlin about, thet the problem could be caused by a different set of permission given from the upgrade process...
– Hoghweed
Sep 21 '13 at 13:58
add a comment |
My laptop is a Linux mint powered host and a windows 8 guest via VMware Workstation.
Yesterday, I get the bad and stupid idea to upgrade my windows 8 to windows 8.1 final release, using the Installer from the ISO.
After everything installed, I logged into my guest windows 8.1, and surprise, I can't map
VMWare Shared Folders as network drive, or simply see, as I could before, "vmware-host" in the list of network locations.
I supposed it could be an issue related to the "TrustedInstaller" user folders ownership, so I tried to update the ownership of system files to the "Administrators" group, but nothing changed.
Anyone has an idea of what can I do, before totally deleting my VM and start again with a new one from scratch?
Thanks in advance
windows-8 security virtualization vmware-workstation
asked Sep 20 '13 at 21:57
Hoghweed
12113
My laptop is a Linux mint powered host and a windows 8 guest via VMware Workstation.
Yesterday, I get the bad and stupid idea to upgrade my windows 8 to windows 8.1 final release, using the Installer from the ISO.
After everything installed, I logged into my guest windows 8.1, and surprise, I can't map
VMWare Shared Folders as network drive, or simply see, as I could before, "vmware-host" in the list of network locations.
I supposed it could be an issue related to the "TrustedInstaller" user folders ownership, so I tried to update the ownership of system files to the "Administrators" group, but nothing changed.
Anyone has an idea of what can I do, before totally deleting my VM and start again with a new one from scratch?
Thanks in advance
windows-8 security virtualization vmware-workstation
windows-8 security virtualization vmware-workstation
asked Sep 20 '13 at 21:57
Hoghweed
12113
asked Sep 20 '13 at 21:57
Hoghweed
12113
asked Sep 20 '13 at 21:57
Hoghweed
12113
asked Sep 20 '13 at 21:57
Hoghweed
12113
asked Sep 20 '13 at 21:57
Hoghweed
12113
12113
What version of Vmware Workstation? They just released v10 which offers Windows 8.1 support. The Vmware tools probably get updated, and the Guest drivers.
– Zoredache
Sep 20 '13 at 22:42
I'm using vmware 10, I know a clean vm windows 8.1 works as a sugar, but my problem has begun after I updated my guest windows 8 to windows 8.1 using the installer
– Hoghweed
Sep 21 '13 at 0:00
After installing the VMWare tools you can shutdown the VM, edit the .VMX file replacing all occurances of "e1000e" with "vmxnet3" then see if things improve. This switches from an emulated Intel network card to a VMware paravirtualized NIC.
– Brian
Sep 21 '13 at 4:11
reinstall the vmware tools in the VM.
– magicandre1981
Sep 21 '13 at 5:40
@magicandre1981 I've done three times but nothing changed.. I saw, while googlin about, thet the problem could be caused by a different set of permission given from the upgrade process...
– Hoghweed
Sep 21 '13 at 13:58
add a comment |
What version of Vmware Workstation? They just released v10 which offers Windows 8.1 support. The Vmware tools probably get updated, and the Guest drivers.
– Zoredache
Sep 20 '13 at 22:42
I'm using vmware 10, I know a clean vm windows 8.1 works as a sugar, but my problem has begun after I updated my guest windows 8 to windows 8.1 using the installer
– Hoghweed
Sep 21 '13 at 0:00
After installing the VMWare tools you can shutdown the VM, edit the .VMX file replacing all occurances of "e1000e" with "vmxnet3" then see if things improve. This switches from an emulated Intel network card to a VMware paravirtualized NIC.
– Brian
Sep 21 '13 at 4:11
reinstall the vmware tools in the VM.
– magicandre1981
Sep 21 '13 at 5:40
@magicandre1981 I've done three times but nothing changed.. I saw, while googlin about, thet the problem could be caused by a different set of permission given from the upgrade process...
– Hoghweed
Sep 21 '13 at 13:58
What version of Vmware Workstation? They just released v10 which offers Windows 8.1 support. The Vmware tools probably get updated, and the Guest drivers.
– Zoredache
Sep 20 '13 at 22:42
What version of Vmware Workstation? They just released v10 which offers Windows 8.1 support. The Vmware tools probably get updated, and the Guest drivers.
– Zoredache
Sep 20 '13 at 22:42
I'm using vmware 10, I know a clean vm windows 8.1 works as a sugar, but my problem has begun after I updated my guest windows 8 to windows 8.1 using the installer
– Hoghweed
Sep 21 '13 at 0:00
I'm using vmware 10, I know a clean vm windows 8.1 works as a sugar, but my problem has begun after I updated my guest windows 8 to windows 8.1 using the installer
– Hoghweed
Sep 21 '13 at 0:00
After installing the VMWare tools you can shutdown the VM, edit the .VMX file replacing all occurances of "e1000e" with "vmxnet3" then see if things improve. This switches from an emulated Intel network card to a VMware paravirtualized NIC.
– Brian
Sep 21 '13 at 4:11
After installing the VMWare tools you can shutdown the VM, edit the .VMX file replacing all occurances of "e1000e" with "vmxnet3" then see if things improve. This switches from an emulated Intel network card to a VMware paravirtualized NIC.
– Brian
Sep 21 '13 at 4:11
reinstall the vmware tools in the VM.
– magicandre1981
Sep 21 '13 at 5:40
reinstall the vmware tools in the VM.
– magicandre1981
Sep 21 '13 at 5:40
@magicandre1981 I've done three times but nothing changed.. I saw, while googlin about, thet the problem could be caused by a different set of permission given from the upgrade process...
– Hoghweed
Sep 21 '13 at 13:58
@magicandre1981 I've done three times but nothing changed.. I saw, while googlin about, thet the problem could be caused by a different set of permission given from the upgrade process...
– Hoghweed
Sep 21 '13 at 13:58
add a comment |
2 Answers
2
active
oldest
votes
First re-install the VMWare tool in the VM, either do a repair or un-install then install.
After that goto settings and make sure the shared folders are "On"
The shared folders are now available via: vmware-hostShared Folders
For easy access in older Windows programs I created a mapped drive e.g. Z: to vmware-hostShared Folders
answered Nov 23 '13 at 5:34
user2024744
111
add a comment |
In my case, this issue was resolved when I installed the new version 9.6.1 of VMware Tools for Windows (Pre 2000) 9.6.1.
(My former work-around - which worked - was to configure a samba drive on my host and access it through the virtual network on my windows 8.1 guest.)
answered Jan 17 '14 at 16:19
edou_art
412
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f648254%2fvmware-workstation-windows-host-shared-folders-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
First re-install the VMWare tool in the VM, either do a repair or un-install then install.
After that goto settings and make sure the shared folders are "On"
The shared folders are now available via: vmware-hostShared Folders
For easy access in older Windows programs I created a mapped drive e.g. Z: to vmware-hostShared Folders
answered Nov 23 '13 at 5:34
user2024744
111
add a comment |
First re-install the VMWare tool in the VM, either do a repair or un-install then install.
After that goto settings and make sure the shared folders are "On"
The shared folders are now available via: vmware-hostShared Folders
For easy access in older Windows programs I created a mapped drive e.g. Z: to vmware-hostShared Folders
answered Nov 23 '13 at 5:34
user2024744
111
add a comment |
First re-install the VMWare tool in the VM, either do a repair or un-install then install.
After that goto settings and make sure the shared folders are "On"
The shared folders are now available via: vmware-hostShared Folders
For easy access in older Windows programs I created a mapped drive e.g. Z: to vmware-hostShared Folders
answered Nov 23 '13 at 5:34
user2024744
111
First re-install the VMWare tool in the VM, either do a repair or un-install then install.
After that goto settings and make sure the shared folders are "On"
The shared folders are now available via: vmware-hostShared Folders
For easy access in older Windows programs I created a mapped drive e.g. Z: to vmware-hostShared Folders
answered Nov 23 '13 at 5:34
user2024744
111
answered Nov 23 '13 at 5:34
user2024744
111
answered Nov 23 '13 at 5:34
user2024744
111
answered Nov 23 '13 at 5:34
user2024744
111
111
add a comment |
add a comment |
In my case, this issue was resolved when I installed the new version 9.6.1 of VMware Tools for Windows (Pre 2000) 9.6.1.
(My former work-around - which worked - was to configure a samba drive on my host and access it through the virtual network on my windows 8.1 guest.)
answered Jan 17 '14 at 16:19
edou_art
412
add a comment |
In my case, this issue was resolved when I installed the new version 9.6.1 of VMware Tools for Windows (Pre 2000) 9.6.1.
(My former work-around - which worked - was to configure a samba drive on my host and access it through the virtual network on my windows 8.1 guest.)
answered Jan 17 '14 at 16:19
edou_art
412
add a comment |
In my case, this issue was resolved when I installed the new version 9.6.1 of VMware Tools for Windows (Pre 2000) 9.6.1.
(My former work-around - which worked - was to configure a samba drive on my host and access it through the virtual network on my windows 8.1 guest.)
answered Jan 17 '14 at 16:19
edou_art
412
In my case, this issue was resolved when I installed the new version 9.6.1 of VMware Tools for Windows (Pre 2000) 9.6.1.
(My former work-around - which worked - was to configure a samba drive on my host and access it through the virtual network on my windows 8.1 guest.)
answered Jan 17 '14 at 16:19
edou_art
412
answered Jan 17 '14 at 16:19
edou_art
412
answered Jan 17 '14 at 16:19
edou_art
412
answered Jan 17 '14 at 16:19
edou_art
412
412
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f648254%2fvmware-workstation-windows-host-shared-folders-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What version of Vmware Workstation? They just released v10 which offers Windows 8.1 support. The Vmware tools probably get updated, and the Guest drivers.
– Zoredache
Sep 20 '13 at 22:42
I'm using vmware 10, I know a clean vm windows 8.1 works as a sugar, but my problem has begun after I updated my guest windows 8 to windows 8.1 using the installer
– Hoghweed
Sep 21 '13 at 0:00
After installing the VMWare tools you can shutdown the VM, edit the .VMX file replacing all occurances of "e1000e" with "vmxnet3" then see if things improve. This switches from an emulated Intel network card to a VMware paravirtualized NIC.
– Brian
Sep 21 '13 at 4:11
reinstall the vmware tools in the VM.
– magicandre1981
Sep 21 '13 at 5:40
@magicandre1981 I've done three times but nothing changed.. I saw, while googlin about, thet the problem could be caused by a different set of permission given from the upgrade process...
– Hoghweed
Sep 21 '13 at 13:58