Help required with new Twinvine setup..

[LastResort]

Hi there all,

1st off... This install is being done on a clean install of windows 11 64bit on a laptop.

Following Angela's info from https://github.com/vinefeeder/TwinVine. and following it letter for letter. I have stumbled across a problem.

I am at the part where i am instructed to do the following:

- Watch the installation, a number of binary files will be downloaded and installed to C:\Tool\bin. Installation will take a while. After finishing, close PowerShell and restart your machine.

4/
- Open Start
- Type PowerShell
- Type uv [return]. Expect to see a screen of help. If uv did not install from the Install-media-tools.ps1 script you will not see any response. Uv is a python package manager.


Images of installation:


[Attachment 92248 - Click to enlarge]


[Attachment 92249 - Click to enlarge]

Error Message:


[Attachment 92250 - Click to enlarge]


Installation went fine, It did take quite a while to download and install everything.

I will be copying over my working envied.yaml from my win 10 pc and adjusting as necessary. any help with the above would be very much appreciated.

[iamghost]

Why did you run cmd in system32 folder?
Did you install python first?

[LastResort]

Hi iamghost,

I just followed the instructions...



Installation for Windows with a bare machine and novice user.

You are going to install all the required binary files and automatically add then to system variable - Path. The Python interpreter will be installed automatically too.

- download git from https://github.com/git-for-windows/git/releases/download/v2.52.0.windows.1/Git-2.52.0-64-bit.exe and run the installer
- re-start your machine
- Open Start
- Type PowerShell and select open PowerShell
- Within PowerShell change directory, chdir, or cd, to your chosen location, where TwinVine is to be installed, and type the following command followed by enter,

ect, ect,


system32... to be honest i didn't know i did... it's a 64bit laptop with 64 bit copy of win11...

[lomero]

system32... to be honest i didn't know i did... it's a 64bit laptop with 64 bit copy of win11...

lol system32 is the core of all SO, 32&64 bit

look on C:\Windows\System32


[Attachment 92257 - Click to enlarge]

[LastResort]

Okay.... thanks for the info lomero..


So does anyone know why i'm getting the error. because the installation seemed to go okay...

[A_n_g_e_l_a]

Okay.... thanks for the info lomero..


So does anyone know why i'm getting the error. because the installation seemed to go okay...

I just love it when folks claim to have followed instructions exactly. Clearly you haven't because uv didn't install.

The guide says:

- Watch the installation, a number of binary files will be downloaded and installed to C:\Tool\bin. Installation will take a while. After finishing, close PowerShell and restart your machine.
- Open Start
- Type PowerShell
- Type uv [return]. Expect to see a screen of help. If uv did not install from the Install-media-tools.ps1 script you will not see any response. Uv is a python package manager.
- If uv is not installed close PowerShell and re-open as administrator, so
- Open Start
- Type PowerShell
- Right-click Windows PowerShell → Run as administrator
- Type powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.9.18/uv-installer.ps1 | iex" [return]

- Close PowerShell and re-start your machine.

I've flagged up the bit you most likely missed in red. "Followed instructions to the letter"

[LastResort]

Thank you for the reply Angela..... I Have done as per your instructions but before I come back with another error, is it normal for powershell as admin to open as PS C:\WINDOWS\system32>

I've been running powershell on my win10 pc for years, but in all honesty I've never really bothered to look at what it actually shows. I've just ran my win10 powershell as admin and it does indeed open in system32>

lomero has planted a seed of doubt in what i'm actually doing.

okay, I've found out that by typing in [intPtr]::size into powershell it shows either a 4 for 32bit or 8 for 64bit. both of mine are running 64bit powershell. So I'm going to go ahead with your instructions outlined above.


[Attachment 92286 - Click to enlarge]

------------------------------


[Attachment 92287 - Click to enlarge]