![]() (At present, there was no option of moving it to a different drive.) System Restore (Win-R > SystemPropertiesAdvanced > System Protection tab) was another potentially large user of space on drive C. So if hibernation was turned on (via powercfg /h on) on the WTG drive, and if I would be using the WTG drive to boot a computer with 32GB RAM, drive C would need to retain permanently at least 12.8GB of unused space for the hiberfil.sys file. In Windows 10 and 11, the size of the hibernation file (hiberfil.sys) was reportedly set at about 40% of RAM unless otherwise configured. When deciding on the size of drive D, I would have to leave enough free space on drive C to accommodate hibernation, if I wanted that. If space permitted, I would use the partitioning tool to create an NTFS partition on the WTG drive, following drive C, and label it as drive D.Also, I normally set the built-in DVD drive, if any, to be drive Y, so that it would not be popping up as drive D or E, thereby interfering with the letters that I preferred to assign to other partitions. If so, I would use the partitioner to remove that drive letter. For instance, Windows might assign a drive letter to the small initial boot partition on the WTG drive. The first task for my partitioner was to review drive letters.If the system was not booting, or if it otherwise required inspection from outside, GParted on a bootable Ubuntu Linux USB drive would work for some purposes. I had installed MiniTool Partition Wizard and others, and could also use those. Disk Management ( diskmgmt.msc) was built-in and was thus always an option. ![]() I found several ways in which it could be useful to start by running a partitioning tool.Activation would permit some changes that would not be available on a non-activated installation. In that context, the WTG installation was likely to be activated. These were best done at the beginning, after using the WTG drive to boot the computer from which it was cloned. Some were one-time tweaks and fixes that, once made on the WTG drive, would work on any computer where the WTG drive might be connected. It developed, however, that it could be helpful and in some regards necessary to refine the WTG clone. Just plug it in, boot it up, and off you go. It may seem that a clone should function exactly as the source drive D. This method was much faster than the AOMEI approach. Briefly, the approach I used in the free edition of DiskGenius was simply to select the physical drive containing drive C, and then go to menu > Tools > System Migration. Instead, I looked for a different solution, and I found one: DiskGenius. That did not occur to me immediately, else I would have experimented to see whether earlier versions of the AOMEI software still provided that functionality. Possibly AOMEI had removed that functionality from its free version. (Note also another post on methods of cloning to a USB drive.)Īs indicated in that previous post, I took various steps to reduce the size of the installation (hence, of the AOMEI image) before making the image I chose to restore that image onto a GPT rather than MBR USB drive and after restoring the image, I made certain adjustments in the BIOS/UEFI setup utility in the computer where I would be booting the resulting USB drive.īy 2023, the AOMEI method had ceased to work. The previous post reviewed various tools that were available at that time (2021), and settled upon the approach of using AOMEI Backupper Standard to create an image of the source computer’s Windows 10 system drive, and then to restore that image onto a USB drive. I have contacted them about this repeatedly, and yet I find it happening once again, in this brand-new post. If you encounter a path that looks like C:Program FilesASUS, you can be pretty sure that what I actually wrote was C:\Program Files\ASUS. Note: I see that WordPress is still stripping out backslashes from my posts. Assuming those claims are accurate, some users may find those alternatives more cost-effective than the free software approach described here. Note especially that some paid programs claim Windows To Go (WTG) functionality. They may still work for situations described in those earlier posts. This update was necessary because the methods discussed in the more recent prior post ceased to work for me. Readers who are not familiar with tools or techniques mentioned here may appreciate the much longer discussion in the 2021 post especially. This post does not attempt to cover all related matters comprehensively. This post provides an update on ( 1 2) previous posts discussing methods of creating a bootable USB drive that runs Windows 10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |