Get-VSSetupInstance error while pulling from Dev

[MohamedIbrahim404]

Common issues

• If you get a "Terminal Services" error message, have you tried the troubleshooting steps from the main instructions?

• If you get a "the setup configuration provider is not registered" error message, have you installed the "Visual Studio C++ Tools"?

• You have tried rebuilding from scratch (Reset your build with ./build.ps1 -Clean, and it will reset your workspace and build.).

Issue

I'm having trouble building build.ps1
i have the vs tools installed and i did pull from the dev however i get the Get-VSSetupInstance error

Expected Behavior

Should build properly

Error Messages

Lockdown Browser Variant

Lockdown Browser (no webcam)

Lockdown Browser Version

2.1.3.00

Windows Version and Build

10.0.26100 2009

Repository version

v1.4.0-3-g6bdd115

Other

I'm not sure if i installed the proper tools or if I'm not pulling from dev correctly or if it's a different issue

[PatrickBatxman]

I just had this issue. Make sure you downloaded the correct SDK for your windows version, and install community with the 3 individual components.

If this doesn't work you can do this to install the VSSetupInstance:

Install-Module -Name VSSetup -Scope CurrentUser -Force -AllowClobber

And check if its installed correctly with:

Get-VSSetupInstance

If still not loaded:

Import-Module VSSetup

[gucci-on-fleek]

@MohamedIbrahim404

Error Messages

[...]

Can you please upload your complete log file? It should be in logs\Build.log.

Lockdown Browser Version

2.1.3.00

Even if you get this to successfully build, it's unlikely that this will work properly. See #132 and #144.

Windows Version and Build

10.0.26100 2009

Are you sure that that's correct? Windows 10 version 2009 is ancient by now, so I kinda doubt that you're using that. The build number 10.0.26100 corresponds to Windows 11 24H2, so I'm guessing that that's what you're actually using.

Other

I'm not sure if i installed the proper tools or if I'm not pulling from dev correctly or if it's a different issue

git describe gave you the expected output, so you seem to have pulled the repository correctly, and your VS installer screenshot seems to have all of the correct boxes checked, which suggests that you've probably installed all of the tools correctly.

---

@PatrickBatxman

I just had this issue. Make sure you downloaded the correct SDK for your windows version, and install community with the 3 individual components.

If this doesn't work you can do this to install the VSSetupInstance:

Install-Module -Name VSSetup -Scope CurrentUser -Force -AllowClobber

And check if its installed correctly with:

Get-VSSetupInstance

If still not loaded:

Import-Module VSSetup

Yes, all excellent suggestions, thanks!

[MohamedIbrahim404]

It did work however i am getting an error from the sandbox itself.
here is the log file

Build.log

[MohamedIbrahim404]

Windows Version and Build

10.0.26100 2009

Are you sure that that's correct? Windows 10 version 2009 is ancient by now, so I kinda doubt that you're using that. The build number 10.0.26100 corresponds to Windows 11 24H2, so I'm guessing that that's what you're actually using.

I just ran the command and this is what i got. i doubt it too as i just bought my laptop recenty

[gucci-on-fleek]

@MohamedIbrahim404

It did work however i am getting an error from the sandbox itself. here is the log file

Build.log

Looking through the log, the build script failed the first few times (@Voidless7125, do you have any idea why???), but on the last run, it seems to have finished successfully. So you should be able to launch the Windows Sandbox and have it work (again, notwithstanding the problems mentioned in #132 and #144).

[Voidless7125]

It did work however i am getting an error from the sandbox itself. here is the log file

Build.log

The sandbox has a different log, sandbox_run.log. Could you also send that to me?
Also @gucci-on-fleek the 2009 thing is a Microsoft issue, that's not from the user. (Try running it on windows 11 and you will get the same output)

As for why it failed to run many times, that's very odd. The second to last was because withdll.exe got deleted by Windows defender, but the build script randomly working is odd. The script should of auto installed it.

[Voidless7125]

@MohamedIbrahim404

It did work however i am getting an error from the sandbox itself. here is the log file

Build.log

Looking through the log, the build script failed the first few times (@Voidless7125, do you have any idea why???), but on the last run, it seems to have finished successfully. So you should be able to launch the Windows Sandbox and have it work (again, notwithstanding the problems mentioned in #132 and #144).

Alright got it down. When the installer does it's thing, it is not added to path yet. Best thing to do is log off and back in. (Not lock and unlock!)