1 |
On 5/23/21 4:04 AM, Michael wrote: |
2 |
>> On Sat, May 22, 2021, 17:02 <thelma@×××××××××××.com> wrote: |
3 |
>>> Is anybody running Windows 10 Pro 64bit in Virtualbox? |
4 |
>>> Is it stable? |
5 |
>>> Is it easy to resize? |
6 |
> |
7 |
> I forgot to mention stability and resizing ... |
8 |
> |
9 |
> In one case after a major update the Win10 desktop became terribly unstable, |
10 |
> menus not showing up, everything on the desktop taking minutes to respond to a |
11 |
> mouse click or keyboard press. Eventually I realised the transparency had |
12 |
> been enabled by the update and this was cause any desktop graphics to render |
13 |
> partially and with a lot of latency. Disabling transparency restored the |
14 |
> previous normal desktop behaviour. This was on a host with an old AMD-Radeon |
15 |
> APU. Other video cards and drivers may not have such a problem, but I thought |
16 |
> it worth mentioning. |
17 |
> |
18 |
> Resizing the C:\ drive partition is straight forward, in most cases. You can |
19 |
> use 'VBoxManage modifyhd' in a terminal to increase the virtual disk size, or |
20 |
> the VBox GUI Virtual Media Manager tab. Then use the Windows Disk Management, |
21 |
> or boot the VM with GParted and resize the OS partition & filesystem. |
22 |
> However, Windows 10 tends to create additional partitions as part of |
23 |
> installation, or subsequent major updates. These are called System Reserve |
24 |
> Partitions (SRP). Initially one is created at the start of the disk to |
25 |
> contain bitlocker, boot and Windows Restore data. After certain major |
26 |
> updates, or if the Windows 10 installation was an in situ upgrade from an |
27 |
> older Windows 7 installation, such an SRP can be placed after the C:\ drive. |
28 |
> In one case, changing an installed system from MBR to GPT/UEFI also created an |
29 |
> ESP after the C:\ drive. It follows you won't be able to increase the size of |
30 |
> the C:\ partition without moving any partitions following it out of the way |
31 |
> first, increasing C:\, then restoring the moved partitions. Since an |
32 |
> otherwise 5 minute disk & partition resizing exercise can develop into a |
33 |
> prolonged and pre-planned effort, you'd be better off sizing up the virtual |
34 |
> disk before you start installing MSWindows. |
35 |
> |
36 |
> Big upgrade releases every six months may require more temporary storage space |
37 |
> to create a backup in case the upgrade fails. If enough space is not |
38 |
> available on the disk, the the OS will ask you to insert a USB drive to be |
39 |
> used during the upgrade. You can also create and attach a new virtual disk |
40 |
> for this purpose. |
41 |
> |
42 |
> Finally, there's the Windows 10 'Storage Spaces' replacing Dynamic Disks, if |
43 |
> you want to create a RAID in software. I understand you use it to add more |
44 |
> disks/partitions, like you would with a RAID, but I have never used this to |
45 |
> know what it can achieve in terms of resizing. |
46 |
|
47 |
Thank Michael for the update. It is handy. |
48 |
When you are talking about "transparency" you mean inside Windows 10, isn't it? |
49 |
|
50 |
I've experimented with resizing Windows 10 32bit (currently installed) using gparted and it went very well, no problems. |
51 |
I'm not sure with switching to Windows 10 64bit will help or not. |