mirror of
https://github.com/VFrontDe-Org/ESXi-Customizer-PS.git
synced 2026-04-25 23:46:02 +03:00
[GH-ISSUE #15] "[WinError 10054] An existing connection was forcibly closed by the remote host" during "Exporting the Imageprofile" #4
Labels
No labels
bug
duplicate
duplicate
enhancement
fix in-progress
invalid
need more info
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ESXi-Customizer-PS#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @reedy on GitHub (Apr 29, 2020).
Original GitHub issue: https://github.com/VFrontDe-Org/ESXi-Customizer-PS/issues/15
I've seen the other tasks, but they seem to be failing on the steps during downloading the images/isos, but I'm getting a failure during the "Exporting the Imageprofile" step... And I can't see why it'd be failing on a web connection related issue when writing a file locally.
It did fail downloading the ISO originally, so I downloaded it manually and stuffed it in the directory, which made it get further
I also disabled the windows firewall...
ESXi-Customizer-PS-17776.log
I guess this might be more an underlying bug with
Export-EsxImageprofile... But I thought I'd try here first :)I was following https://andrewroderos.com/vmware-esxi-home-lab-intel-nuc-frost-canyon/ which said to run
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypassbut that failed@cybero2912 commented on GitHub (May 5, 2020):
same here :(
@pantigon commented on GitHub (May 11, 2020):
me too...:D
@hansnull commented on GitHub (May 11, 2020):
same here, issued command was:
.\ESXi-Customizer-PS.ps1 -v67 -vft -load sata-xahci,net55-r8168,net51-r8169
@spinmyego commented on GitHub (May 12, 2020):
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v2.0.50727]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v2.0.50727]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
@reedy commented on GitHub (May 13, 2020):
I'm not sure how changing .NET crypto (and why in multiple different versions/variants) helps solve a problem when it's supposed to be writing things to disk, not reading stuff from the internet..
@pantigon commented on GitHub (May 14, 2020):
error when used: ".\ESXi-Customizer-PS.ps1-v70 -vft -load sata-xahci,net55-r8168"
@Chavell3 commented on GitHub (May 17, 2020):
Hey there,
I'm having the same issue like the others before...
When exporting the image I get the error message.
I also tried the reg-keys above, but this doesn't help...
Is there any help for that?
@mr-craps commented on GitHub (May 18, 2020):
Hey there!
Try to create an offline bundle in front of the install iso by using the the parameter
-ozip.After creation, you can use that file to create the installation iso with
-izip.Replace <bundle> with the name of the created offline bundle (e.g. ESXi-7.0.0-15843807-standard)
That worked for me :)
@mwilson6491 commented on GitHub (Jun 16, 2020):
To include offline bundles to inject NIC drivers, the -pkgDir option can be added to the -ozip line. This assumes the offline bundle packages are in the same directory as the script.
.\ESXi-Customizer-PS.ps1 -ozip -pkgDir ./
@Nevexo commented on GitHub (Jul 3, 2020):
Combining the two comments above, if you're wanting to load the net drivers, this works:
@cddisk2000 commented on GitHub (Jul 10, 2020):
@reedy @cybero2912 @pantigon
use this PowerCLI version ==> Install-Module -Name VMware.PowerCLI -RequiredVersion 10.2.0.9372002
i meet same error [WinError 10054] ......... I don't understand how to solve this problem
ESXi-6.7.0-20200604001-standard-customized-202007110209.log
@virtualex-itv commented on GitHub (Jul 10, 2020):
If a WinError 10054 is encountered, run the following commands then reboot your machine and retry:
[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Ssl3@reedy commented on GitHub (Jul 11, 2020):
I don't see how that will help; It's supposed to be writing something to disk, not making network connections to wherever
@virtualex-itv commented on GitHub (Jul 11, 2020):
It works as I’ve used this fix numerous times but it’s up to you if you want to use it or not
@reedy commented on GitHub (Jul 11, 2020):
Obviously. But there's not much point making changes arbitarily without understanding if/how they actually help
Do you just run every command someone on the internet tells you to to fix an issue?
Like, why do I need to enable SSL3? Considering it's a pretty broken format... https://disablessl3.com/
@reedy commented on GitHub (Jul 11, 2020):
Does the vmware tool communicate with itself or different parts using a local HTTP server using HTTPS?
Even then, it hardly explains why I need apparently both SSL3 and TLS1.2?
@virtualex-itv commented on GitHub (Jul 11, 2020):
I understand what you mean and unfortunately I don’t have the answers for you. I just wanted to simply provide a solution that I’ve tried which I know worked for me and could potentially help others.
@virtualex-itv commented on GitHub (Jul 13, 2020):
OK, running a fresh installation of Windows 10 (2004) x64 and latest PowerCLI from PSGallery...
I was not presented with this issue and am unable to reproduce. Export competed successfully, so this is not an issue with the script...
@virtualex-itv commented on GitHub (Jul 17, 2020):
apparently - that was short lived. After doing some more research, it seems that the website from where the images are pulled from requires SSL3 to connect and pull properly. (I agree that it shouldn't require this but I have no control over that)
After running
[Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Ssl3to add SSL3 support in PowerShell and rebooting the computer, the script executes as expected every time. I will see if I can bring this up internally.@virtualex-itv commented on GitHub (Jan 5, 2021):
FYI - a possible solution is being tested. Thanks for your patience. :)
@virtualex-itv commented on GitHub (Oct 18, 2022):
workaround added into v 2.8.2 and later