oscdimg does not support long path

[LaurentLouf]

Hello,

First of all thanks for the great tool, it is really helpful !

I have however stumbled upon a limitation with one of the ADK executables, oscdimg, that does not seem to support long path (> 260 characters). As an easy fix, I've tried mapping the Apps folder as a drive using the command subst. But well, what should have happened has happened and I'm still stuck with another path that is too long.

Too bad as oscdimg is a nice one-liner but I'll try with https://github.com/TheDotSource/New-ISOFile and keep you posted here.

[rbalsleyMSFT]

Can you try setting LongPath support?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

Set LongPathsEnabled = 1 (REG_DWORD)

Let me know if that works (preferably without a reboot). If it works without a reboot, we could make the change in the script to enable it and then set it back when finished. I've actually run into issues with long paths and driver downloads (can't remember the exact problem, think BITS didn't like the length of the path or something). So it's possible this fix could help a couple of things.

[LaurentLouf]

Seems like I forgot to mention that I did try that without success. The register and the group policy (though they might be the same thing)

[rbalsleyMSFT]

Did you try a reboot? From: Laurent Louf ***@***.***> Sent: Wednesday, September 18, 2024 11:27 AM To: rbalsleyMSFT/FFU ***@***.***> Cc: Richard Balsley ***@***.***>; Comment ***@***.***> Subject: Re: [rbalsleyMSFT/FFU] oscdimg does not support long path (Issue #80) Seems like I forgot to mention that I did try that without success. The register and the group policy (though they might be the same thing)

On Wed, Sep 18, 2024, 7:18 PM rbalsleyMSFT ***@***.***<mailto:***@***.***>> wrote: Can you try setting LongPath support? HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem Set LongPathsEnabled = 1 (REG_DWORD) Let me know if that works (preferably without a reboot). If it works without a reboot, we could make the change in the script to enable it and then set it back when finished. I've actually run into issues with long paths and driver downloads (can't remember the exact problem, think BITS didn't like the length of the path or something). So it's possible this fix could help a couple of things. - Reply to this email directly, view it on GitHub <#80 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDS626V4S23SSGH6RC5XHDZXGYXDAVCNFSM6AAAAABONFH4DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJZGAYTQMJZG4> . You are receiving this because you authored the thread.Message ID: ***@***.***<mailto:***@***.***>>

- Reply to this email directly, view it on GitHub<#80 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYE2BGMCIWBHXPXGEDCHCDZXHAYTAVCNFSM6AAAAABONFH4DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJZGE2DCNBYGE>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[LaurentLouf]

I already had to set this registry key a long time ago, so I didn't need to set actually this time. Since I didn't have to change the value, I also didn't reboot as there was nothing to "apply". By the way, the New-ISOFile that I mentioned at the beginning is working as far as I know as expected

[rbalsleyMSFT]

I think we need to do two things.

1. Enable Long Path support
2. Use \\?\ in front of the apps path

With just Long Path support enabled in the registry, I can get a script to create a path longer than 300 characters, but oscdimg fails to create the ISO. If I don't add the long path support, it doesn't create the complete directory path

If I add \\?\ in front of the directory path to generate the ISO, it works.

Can you try modifying the New-AppsISO function by adding:

$appsPath = "\\?\" + $appsPath #Add the \\?\ prefix to the path to allow for long file names

before

Invoke-Process $OSCDIMG "-n -m -d $Appspath $AppsISO"

Seems to create the ISO for me without an issue. I don't have any apps though with the pathing issues you do, so it'd be good to know if this works for you. If it does, I'll need to add Long Path support plus this fix.

[LaurentLouf]

Well I didn't know this trick with ? but that seems to work.

By the way, I noticed that sometimes when settings $OSCDIMG, you check if we're on an amd64 architecture or ARM64, but not when creatings the Apps ISO, I guess you missed that one !

[rbalsleyMSFT]

Thanks, glad to hear it's working.

Are you building on ARM64 devices?

[LaurentLouf]

No, just amd64