Custom Query (16363 matches)
Results (1129 - 1131 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18352 | invalid | Current state snapshot deleted | ||
| Description |
how to start VM without snapshot state, unfortunately I have deleted current VM state snapshot |
|||
| #18350 | invalid | Windows Backup/Restore does not recognise virtual HDD | ||
| Description |
Using Windows 7 Home Premium 64 bit Host and running Windows 7 Home Premium 64bit guest I have noticed that when trying to restore a guest backup created by Windows Backup/Restore that it cannot recognise the virtual drive HDD to restore the image. The same WindowsImageBackup loads just fine when used on a real computer. |
|||
| #18345 | fixed | Read-only flag of shared folders: not handled properly under Windows Host Linux Guest => Fixed in SVN | ||
| Description |
It is a known issue for Windows that read-only bit for directory has special meanings: it does not really mean read-only. Please see below for the KB article on this subject: https://support.microsoft.com/en-gb/help/326549. Basically, read-only for a directory under Windows is ignored by Windows, and only used by File Explorer as a flag such that desktop.ini file will be used for folder customization. For instance, user Documents directory is read-only by default, yet users have no problem to modify files in it. This applies to Windows 10 as well. Currently, Virtualbox takes the face value of the read-only bit of shared folders under Windows Host, yet it is not the correct interpretation of read-only bit for Windows directories. A quick search will find many reports of VBox shared folder read-only issues. Many time, users would like to access Documents, Download under Linux Host. Yet, these special folders would have strange behaviors under the guest. I believe OS X guest suffers from the same issue. |
|||

