Opened 7 years ago
Last modified 7 years ago
#17192 new defect
5.2 Guest Extension : no share Drives ?!
| Reported by: | Xbase++ | Owned by: | |
|---|---|---|---|
| Component: | guest additions | Version: | VirtualBox 5.2.0 |
| Keywords: | no share drives | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
1.) have upgrade from 5.1.30 and run 5.2 OK. than install Guest Extension. 2.) after reboot i want to reject CD and saw NO share Drives any more ? 3.) after change User i complete lost setup information so i have to attach VDI again and make all setup entry both Windows 10 1703 Host 64bit / Guest 32bit
Change History (6)
comment:1 by , 7 years ago
comment:3 by , 7 years ago
As I said, the bugtracker is not the best place for discussions, or confirmations. Try the forums, way more eyes there...
comment:4 by , 7 years ago
THX for Answer. i do not want to discuss the (95%) Problem, i want to report (5%) it ! i have deinstall v5.2 an went back to v5.1.30 where Guest Extension SHOW share Drive.
comment:5 by , 7 years ago
You might be in the 95% that do not actually have a bug, but hey... I hope that 5.1.30 will serve you well in the years to come.
comment:6 by , 7 years ago
as Developer i knew about last 5%. sometimes i got Error Msg from Customer which i can't confirm with my Hardware but i saw the Error at my Customer. while virtualBox have virtual Hardware i guess it must be the same for all User ... but this is only 95% so there is always 5% left.
i knew how hard it is to find these last 5% special when only 1 Customer have a Problem but in this case it seems to be at least 2 User with different OS which have the same Problem.
THX again for Answer and your great Work.
p.s. it was announced that Windows 10 will default disable SMB1. this start with insider Preview 10.16257 ( Powershell Get-SmbServerConfiguration ) i was surprised when Redstone3 10.16299.19 still have SMB1 enable while i thought that might be the Problem of virtualBox share Drives.
May I suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
So, if you can, please open a new thread in the VirtualBox on Windows Hosts section of the forums.
Please be sure to mention that you came from the bug tracker and include the ticket number.