Launching Wsb (Windows Sandbox Config file) gives error

English support forum

Moderators: white, Hacker, petermad, Stefan2

User avatar
Rex
Junior Member
Junior Member
Posts: 51
Joined: 2003-10-30, 01:05 UTC

Launching Wsb (Windows Sandbox Config file) gives error

Post by *Rex »

When trying to launch a Wsb file from within Tcm I get the error Access Denied on file X:\Test.wsb "Application Not found"
Launching the same file from Explorer opens Windows Sandbox as it should.
Right click and open with, works as it should.
I also tried from FreeComander XE, and there Sandbox is also launched as it should.

I'm on Windows 10 1903 (Build 18362.30) x64

Cheers
/Rex
Personal License #58082
User avatar
Horst.Epp
Power Member
Power Member
Posts: 6482
Joined: 2003-02-06, 17:36 UTC
Location: Germany

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Horst.Epp »

This Windows version is not yet public available.
You will have to live with such problems
until all tools will support all new functions.
Windows 11 Home x64 Version 23H2 (OS Build 22631.3447)
TC 11.03 x64 / x86
Everything 1.5.0.1372a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.73
QAP 11.6.3.2 x64
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48079
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *ghisler(Author) »

How do you create wsb files? I have a Windows 10 1903 preview build (insider fast track) but have no idea what wsb is...
Author of Total Commander
https://www.ghisler.com
User avatar
Dalai
Power Member
Power Member
Posts: 9387
Joined: 2005-01-28, 22:17 UTC
Location: Meiningen (Südthüringen)

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Dalai »

Do you use TC 32-bit or TC 64-bit?

Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64

Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
User avatar
petermad
Power Member
Power Member
Posts: 14796
Joined: 2003-02-05, 20:24 UTC
Location: Denmark
Contact:

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *petermad »

2Rex
Maybe you need to run TC as administrator to launch your Wsb file
License #524 (1994)
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48079
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *ghisler(Author) »

I doubt that. But he could try to open it via right click context menu (or Shift+F10).
Author of Total Commander
https://www.ghisler.com
User avatar
Rex
Junior Member
Junior Member
Posts: 51
Joined: 2003-10-30, 01:05 UTC

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Rex »

Hi
Sorry for the late reply.

@horst.epp
I know, my version is not public yet - but it should soon be rolled out for the public.

@ghisler
the wsb file is just a xml file that looks like this

Code: Select all

<Configuration>
<MappedFolders>
   <MappedFolder>
     <HostFolder>C:\SandboxScripts</HostFolder>
     <ReadOnly>true</ReadOnly>
   </MappedFolder>
   <MappedFolder>
     <HostFolder>C:\CodingProjects</HostFolder>
     <ReadOnly>false</ReadOnly>
   </MappedFolder>
</MappedFolders>
<LogonCommand>
   <Command>C:\users\wdagutilityaccount\desktop\SandboxScripts\VSCodeInstall.cmd</Command>
</LogonCommand>
</Configuration>
Found here https://techcommunity.microsoft.com/t5/Windows-Kernel-Internals/Windows-Sandbox-Config-Files/ba-p/354902
One can use it to make minor configs to the new Windows Sandbox

@dalai
I did try to run the file from a 32bit TC

@petermad
I'm always running as admin UAC is disabled fully

@ghisler
Yeah it works when using rclick.

But sins I can launch the wsb file from Explorer and FreeCommander, my guess was that something in TC was blocking the wsb file, or something like that.

Edit: Just tried with the x64 TC, and there the wsb file functions as it should, it event got an Icon now :D
So I guess that it's x32 that have trouble with the wsb file?

Cheers
/Rex
Personal License #58082
User avatar
Dalai
Power Member
Power Member
Posts: 9387
Joined: 2005-01-28, 22:17 UTC
Location: Meiningen (Südthüringen)

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Dalai »

2Rex
Please do the following in TC 32-bit: Place the cursor on any .wsb file, select menu Files > Associate with. Post the full command line here that's shown in the "Associate with" text field.

I suspect that the command line is only valid within x64 programs, perhaps because it only exists in the native Windows\system32 directory.

Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64

Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
User avatar
Rex
Junior Member
Junior Member
Posts: 51
Joined: 2003-10-30, 01:05 UTC

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Rex »

@Dalai

Code: Select all

Windows.Sandbox (C:\WINDOWS\System32\WindowsSandbox.exe "%1")
Personal License #58082
User avatar
Dalai
Power Member
Power Member
Posts: 9387
Joined: 2005-01-28, 22:17 UTC
Location: Meiningen (Südthüringen)

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Dalai »

OK, do you see that file in TC 32-bit? Do you see it in TC 64-bit?

Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64

Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
User avatar
Rex
Junior Member
Junior Member
Posts: 51
Joined: 2003-10-30, 01:05 UTC

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Rex »

I see the file in both, but as I wrote in x64 it has an sandbox icon, in x32 it dosn't.
Personal License #58082
User avatar
Dalai
Power Member
Power Member
Posts: 9387
Joined: 2005-01-28, 22:17 UTC
Location: Meiningen (Südthüringen)

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Dalai »

I wasn't refering to the .wsb file but the WindowsSandbox.exe (that's why I asked you about the file type association). If the EXE file doesn't exist in C:\Windows\system32 directory from a 32-bit point of view, it can't be opened because the program "is missing". Hence you get the error message "Application not found".

Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64

Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
User avatar
Rex
Junior Member
Junior Member
Posts: 51
Joined: 2003-10-30, 01:05 UTC

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Rex »

Ahh now I get it :D
I can only see WindowsSandbox.exe in x64, so as you says when .exe don't exists file can't be open with it :/

Thx for clearing that up, guess that I just need to create a wrapper that launches my wsb file in 64bit mode from tc x32
Personal License #58082
User avatar
petermad
Power Member
Power Member
Posts: 14796
Joined: 2003-02-05, 20:24 UTC
Location: Denmark
Contact:

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *petermad »

2Rex
you can use C:\WINDOWS\Sysnative\WindowsSandbox.exe in stead of C:\WINDOWS\System32\WindowsSandbox.exe in TC 32bit.

Also see:
On 64-bit Windows versions, some files and folders shown by Windows Explorer are not shown by Total Commander!

Windows x64: Explorer vs TC: Content of System32 different
License #524 (1994)
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
User avatar
Rex
Junior Member
Junior Member
Posts: 51
Joined: 2003-10-30, 01:05 UTC

Re: Launching Wsb (Windows Sandbox Config file) gives error

Post by *Rex »

Cool thx :)
/Rex
Personal License #58082
Post Reply