[GH-ISSUE #25] Issue with 67 Image Build #11

New issue

Closed

opened 2026-02-28 02:14:14 +03:00 by kerem · 3 comments

kerem commented

2026-02-28 02:14:14 +03:00

Owner

Originally created by @praval1983 on GitHub (Jul 19, 2020).
Original GitHub issue: https://github.com/VFrontDe-Org/ESXi-Customizer-PS/issues/25

The following commands can successfully create ISO for ESXi65 build.

`
PS C:\67> [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Ssl3

PS C:\67> .\ESXi-Customizer-PS.ps1 -v65 -vft -nsc -load net-igb -remove vmkusb -log C:\67\ISO\ESXi-Customizer-PS.log -outDir C:\67\ISO
`

However, the same way I am not able to create ISO for ESXi67 build.

`
PS C:\67> [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Ssl3

PS C:\67> .\ESXi-Customizer-PS.ps1 -v67 -vft -nsc -load net-igb -remove vmkusb -log C:\67\ISO\ESXi-Customizer-PS.log -outDir C:\67\ISO
`

See a successful log for 65 build and un-successful 67 builds in the attached log.zip file.

Log.zip

Although I followed Alex Lopez's recomendation to turn on Ssl3 to work around "[WinError 10054] An existing connection was forcibly closed by the remote host" error, it's not a good idea to use Ssl3 given poodle vulnerability which was disclosed a few years ago.

Especially by updating protocol and cipher preferences, you can easily fix/address this on V-Front Online depot.
Given the above workaround seems to have worked for 65 and failed for 67, we can focus in that area.

Given I am not so savvy with Powershell, I would still try to understand 67 image build portion in this PowerShell script and share if I can find anything intrsting.

Originally created by @praval1983 on GitHub (Jul 19, 2020). Original GitHub issue: https://github.com/VFrontDe-Org/ESXi-Customizer-PS/issues/25 The following commands can successfully create ISO for ESXi65 build. ` PS C:\67> [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Ssl3 PS C:\67> .\ESXi-Customizer-PS.ps1 -v65 -vft -nsc -load net-igb -remove vmkusb -log C:\67\ISO\ESXi-Customizer-PS.log -outDir C:\67\ISO ` However, the same way I am not able to create ISO for ESXi67 build. ` PS C:\67> [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Ssl3 PS C:\67> .\ESXi-Customizer-PS.ps1 -v67 -vft -nsc -load net-igb -remove vmkusb -log C:\67\ISO\ESXi-Customizer-PS.log -outDir C:\67\ISO ` See a successful log for 65 build and un-successful 67 builds in the attached log.zip file. [Log.zip](https://github.com/VFrontDe/ESXi-Customizer-PS/files/4944734/Log.zip) Although I followed Alex Lopez's recomendation to turn on Ssl3 to work around "**[WinError 10054] An existing connection was forcibly closed by the remote host**" error, it's not a good idea to use Ssl3 given poodle vulnerability which was disclosed a few years ago. Especially by updating protocol and cipher preferences, you can easily fix/address this on V-Front Online depot. Given the above workaround seems to have worked for 65 and failed for 67, we can focus in that area. Given I am not so savvy with Powershell, I would still try to understand 67 image build portion in this PowerShell script and share if I can find anything intrsting.

kerem

2026-02-28 02:14:14 +03:00

closed this issue
added the
invalid
label

kerem commented

2026-02-28 02:14:15 +03:00

Author

Owner

@virtualex-itv commented on GitHub (Jul 20, 2020):

Did you reboot after running the command to enable Ssl3?

@virtualex-itv commented on GitHub (Jul 20, 2020): Did you reboot after running the command to enable Ssl3?

kerem commented

2026-02-28 02:14:15 +03:00

Author

Owner

@praval1983 commented on GitHub (Jul 20, 2020):

Yes. I did reboot my computer after enabling ssl3 it doesn't change the outcome.
just to clear any doubt. I executed above command to enable ssl3 and rebooted and tried again and still I have same error while creating 6.7 iso.

It's surprising to me that the same computer same configuration and I can create 6.5 ISO without any issue.

@praval1983 commented on GitHub (Jul 20, 2020): Yes. I did reboot my computer after enabling ssl3 it doesn't change the outcome. just to clear any doubt. I executed above command to enable ssl3 and rebooted and tried again and still I have same error while creating 6.7 iso. It's surprising to me that the same computer same configuration and I can create 6.5 ISO without any issue.

kerem commented

2026-02-28 02:14:15 +03:00

Author

Owner

@virtualex-itv commented on GitHub (Jan 5, 2021):

i believe this has something to do with the driver you are trying to load into the image not being supported on any version of vSphere higher than -v65. Most, if not all of the drivers available via -vft -load are legacy and have not been maintained or lack support for newer versions of vSphere due to architectural changes.

@virtualex-itv commented on GitHub (Jan 5, 2021): i believe this has something to do with the driver you are trying to load into the image not being supported on any version of vSphere higher than `-v65`. Most, if not all of the drivers available via `-vft -load` are legacy and have not been maintained or lack support for newer versions of vSphere due to architectural changes.

kerem referenced this issue

2026-02-28 02:14:35 +03:00

[PR #11] [CLOSED] minor fix - add version to help #70