Could not load file or assembly?

[timmetcalfe]

Hi,
I've installed MigrationTools-16.0.9 using first Winget and then downloading the zip file and extracting to a new directory. When running devopsmigration or devopsmigration.exe from the command line, I get the following error:

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Extensions.Hosting.Abstractions, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The system cannot find the file specified.
   at VstsSyncMigrator.ConsoleApp.Program.<Main>d__0.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   at VstsSyncMigrator.ConsoleApp.Program.Main(String[] args)
   at VstsSyncMigrator.ConsoleApp.Program.<Main>(String[] args)

Any ideas?

Thank you for any assistance.

Regards

Tim Metcalfe

[ser789654]

I have same issue.

[MrHinsh]

This can happen for one of two known reasons:

1. Manually download the .zip from GitHub for installation - This is Windows Defender protecting you.
2. Install using Winget as Administrator - This is a bug in Winget 1.6 (fixed in 1.9 but its not out yet)

---

FIX: Manually downloading the .zip from GitHub for install

This usually only happens for manual installs of portable applications downloaded from the internet. Did you use a downloaded .zip?

The install instructions for manual downloads has the following:

NOTE: You may need to ‘unlock’ the downloaded archive before you unzip and run it. Go to the file properties (click Show more options on Win11) and click Unblock.

---

FIX: Install using Winget as Administrator

There is a bug in Winget that doesn't create the correct PATH variable if run in an elevated command prompt. If you uninstall it and rerun the installation on a non-elevated command prompt, it creates the correct PATH.

Winget has fixed the issue, but we are waiting for the new Schema to be available.

---

Can you confirm if this works and which option helped?

[ser789654]

Yes you are right, Admin was the issue. Switched to regular user and tool is starting. Thnx.

[timmetcalfe]

I didn't realise I was the admin on the VM I was using. I've now logged in as an ordinary user, run the Winget install and it works. Thanks for your help and apologies for not realising.

[MrHinsh]

We are pushing out the fix provided by Winget to our schema now. Its already in Preview...

[MrHinsh]

Ive sumitted it to prod... just waiting for the Winget robots to call the moderators.