Jump to content


  • Posts

  • Joined

  • Last visited

kachunkachunk's Achievements


Newbie (1/3)



  1. Sorry from myself as well, haha - I'm not against checking out Cloud Drive for this use case as well, especially if it simplifies things and still pools space and allows for some duplication/redundancy. The vhd-mount stuff can be a bit fickle for inexplicable reasons, just rarely and randomly. I sometimes still see update issues as well, but it could be unrelated. Nevertheless, can you elaborate on how Store apps would behave in contrast, on Cloud Drive, Drashna?
  2. Oh, I didn't realize you needed the Hyper-V role installed to mount vhd/vhdx files/disks, but I suppose it makes some sense if you squint hard enough. I just had it enabled before-hand for other reasons. If you haven't already, be sure you perform a reboot test and ensure the disk auto-mounts on boot (after you set up that scheduled task, per step 7). Related to the Hyper-V role - If it's enabled nowadays, Virtualization Based Security (VBS) can prevent other hypervisors from working properly in it (VT extensions don't get exposed to the other hypervisor). Mainly you just need to ensure you're on a current update level for the now "nested" hypervisor (like VMware Workstation 15.5 and later). Some Android emulators like Nox (technically on VirtualBox) might not run well without updating it as well, mainly because it's running without its desired passed-through VT extension. Anyway, happy that helped you! It's been a while but so far everything is running strong. I haven't had any update hiccups since, and reboots are completely uneventful. Edit: Okay, I think I narrowed it down to a specific feature: "Hyper-V Module for Windows PowerShell," nestled within the Hyper-V feature tree, so I've made an edit in my previous comment. You otherwise shouldn't need to enable the entire Hyper-V feature if you don't want to. There may be other commands to mount a .vhd/vhdx file without using that particular PowerShell commandlet as well. This is a bigger issue/concern for Home edition users since Hyper-V is not available for them without upgrading.
  3. Hey gang, I searched around and wanted to see if I could find the best topic to reply to, rather than submitting a new thread. But I can do that if preferred. TL;DR - there's a decent workaround: Create a virtual disk (.vhdx / dynamically sized) on your Drive Pool via Windows Disk Management, format it as NTFS with a 4K cluster size, assign it a drive letter, then install your apps to it. Longer version: From my understanding from this, the EFS implementation in Windows produces far too many unreasonable hurdles for filters and other filesystems to interoperate with Windows Store Apps (inclusive of Xbox Games Pass content). Among other things. The EFS... stack? also makes the assumption that the filesystem's cluster size is 4KB. So if you're using something other than that, it leads to update errors eventually, even if you seemingly had no issues downloading and installing store apps originally. From Googling the original error code, it appeared that it was somewhat common on cloud gaming service VMs, as they often deploy with disks formatted with >4KB cluster sizes, which is the root of this archaic issue. I had the same errors on a Storage Space formatted as NTFS with 16KB sectors (all before I moved to Drive Pool!). Sidenote - I don't know why that was the default allocation unit size, but by the time I discovered this, there was no way I was going to evacuate the filesystem to reformat it. My guesses are that it's due to volume size (20TB), or simply because Storage Space defaults are that way out of some memory or I/O management efficiency. [Edit: 2021-01-07] So, the workaround that seemed to work for everyone was to create a virtual disk. You might have issues mounting the disk without the "Hyper-V Module for Windows PowerShell" feature installed/enabled. This comes with Hyper-V if you choose to install that, but the specific module should be installable without, I imagine. Still, the biggest concern is that I'm not sure if this is available in Home edition users or not. So, in case it helps, here's a link to a bunch of ways to mount a virtual disk: https://www.tenforums.com/tutorials/61391-mount-unmount-vhd-vhdx-file-windows-10-a.html. You mainly want to try to find a process that can be done via command-line, so you can automate it in a startup task. You really want this disk mounting on startup. Creating your virtual disk and auto-mounting it: Open Disk Management in Windows. Select a Drive Pool, or another desired volume to store your virtual disk. Under the Action menu, click Create VHD. Follow the simple steps to create and size the disk. Locate the new disk in Disk Management (at the bottom, probably. It'll have a blue icon). Initialize the disk (likely GPT), then create a new Simple volume. NTFS, 4096-byte allocation unit size (4K clusters). Optionally give it a label, assign it a drive letter. [Edit: 2020-10-15] Create a scheduled task to auto-mount your .vhdx file on startup. I used the steps documented here: https://www.tenforums.com/tutorials/138629-auto-mount-vhd-vhdx-file-startup-windows-10-a.html However if you're running Windows 10 Home edition, you may need to refer to the other link above in section 3, for more options. Finally, start using the disk. In the Xbox app, go to Settings -> General, then under Game Install options, specify your new virtual drive's letter under "Change where this app installs games by default." Go start downloading and installing games. In the Apps & Features settings page, you can also right-click and move preexisting Xbox/Store Apps if you need to.
  • Create New...