kit icon indicating copy to clipboard operation
kit copied to clipboard

Installation Failure on Windows

Open st0le opened this issue 3 years ago • 8 comments

Error: write EOF
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)

Kit 1.39.24 Electron 22.0.0 win32 10.0.22622 Locale: en-US

st0le avatar Dec 20 '22 19:12 st0le

@st0le Can you please try the Windows build from here?

https://github.com/johnlindquist/kitapp/releases/tag/v1.40.1

johnlindquist avatar Dec 22 '22 19:12 johnlindquist

Issue is still there on new version also.

UnitedWithCode avatar Dec 29 '22 12:12 UnitedWithCode

I need more details:

Are you an admin on your machine? Are you on a VPN? Is there anything on your machine that you think might interfere with an app?

We have many Windows users using it without any issues. So I'll need help trying to reproduce what's different about your machines.

johnlindquist avatar Dec 29 '22 14:12 johnlindquist

  • Yes. I am admin of machine.
  • No, I am not running VPN.
  • Nothing is interfering with machine. I am running multiple Node projects.

I was facing issue with installation. Came across this GitHub issue. Removed everything from previous install. Went ahead with your instruction with updated version. Same issue persist.

UnitedWithCode avatar Dec 29 '22 14:12 UnitedWithCode

@UnitedWithCode Does the install get far enough to see any logs?

%USERPROFILE%.kit/logs/kit.log %USERPROFILE%\AppData\Roaming\Kit\logs\main.log %USERPROFILE%\AppData\Roaming\Kitlogs\update.log

Do you see the splash screen when you install, or does it fail before anything happens?

johnlindquist avatar Dec 29 '22 14:12 johnlindquist

Hello!

I was having problems with the installation but after checking the logs in %USERPROFILE%\AppData\Roaming\Kit\logs\main.log y noticed that there was an error in the installation of node.

The error was:

[2023-01-12 09:42:27.217] [error] Error: EPERM: operation not permitted, rename 'C:\Users\isman\.knode\node-v16.17.1-win-x64' -> 'C:\Users\isman\.knode\bin'

After that, I renamed manually the folder node-v16.17.1-win-x64 to bin and relaunch the install process and it looks like it is working now.

Hopes that it helps you in the process of debugging

ismanapa avatar Jan 12 '23 08:01 ismanapa

Can confirm this worked. ty @ismanapa

st0le avatar Jan 17 '23 19:01 st0le

@ismanapa Awesome, thanks for debugging and letting me know the fix. Super helpful since I wasn't able to reproduce. I'll see what I can do fix the setup process for future users.

johnlindquist avatar Jan 17 '23 21:01 johnlindquist