build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | 0 skipped | | format
apiVersion: soultec.ch/v1kind: Postmetadata: name: vmware-releases-6-5-update-1 locale: en labels: author: dario-doerflinger capability/virtualization: 1.37 vendor/vmware: 0.88 annotations: source: blog-content/posts/en/vmware-releases-6-5-update-1.md route: /en/insights/vmware-releases-6-5-update-1/ schema: /nerd/schema/posts.json markdown: /en/insights/vmware-releases-6-5-update-1.mdspec: title: vSphere 6.5 Update 1 date: 2017-07-31 author: dario-doerflinger locale: en summary: >- A couple of days ago VMware released version 6.5 Update 1 for some of their products: vCenter Server: Link ESXi: Link, Link to HPE Custom Image Site Recovery Manager (SRM): Link I was waiting for capabilities: [virtualization] vendors: [vmware] legacySlug: vmware-releases-6-5-update-1 migrated: 2026-08-24 draft: false sections: - body: | A couple of days ago VMware released version 6.5 Update 1 for some of their products: - vCenter Server: [Link](https://my.vmware.com/group/vmware/details?downloadGroup=VC65U1&productId=614&rPId=17343) - ESXi: [Link](https://my.vmware.com/group/vmware/details?downloadGroup=ESXI65U1&productId=614&rPId=17343), [Link to HPE Custom Image](https://my.vmware.com/group/vmware/details?downloadGroup=OEM-ESXI65U1-HPE&productId=614) - Site Recovery Manager (SRM): [Link](https://my.vmware.com/group/vmware/details?downloadGroup=SRM651&productId=617&rPId=17333) I was waiting for Update 1 of the vSphere Stack for a while now, and the List of bugfixes has quite a few entries with critical bug fixes. - heading:

Installation Update 1 on 6.5 VCSA

body: | The Update process is incredibly fast. Attach the .iso to your VCSA VM. Go the VAMI (https://<your-vcenter>:5480) and select the Update Tab. Choose to check for Updates on CD-ROM and then install the updates. After about 4 minutes the installation is done and you'll need to manually reboot the appliance. That's it you're done. Upgrading from vSphere 6.0 Update 3 is now fully supported with 6.5 Update 1. - heading:

Upgrading ESXi hosts to 6.5 Update 1

body: | With ESXi hosts there are many roads to choose from. - Patch using VMware Update Manager - Upgrade using VMware Update Manager (Upload the iso file) - Re-Install using the latest image and kickstart script In my Lab where we still use HPE G7 hardware (I know, it's not supported, but it still works and it's a lab..) I had a couple of problems. Using the iso with VUM did not work. Next I got a purple screen when doing a fresh install with the latest HPE Image (see link above). The exception was of type 14 (seems to be a page fault according to VMware KBs) so I'm not sure if it's because the hardware is not supported anymore or if I have some hardware issues. Anyways, I'll be working on that and I'm sure I'll get it to work and update my findings here. - heading:

Upgrading SRM to 6.5 Update 1

body: | For this upgrade to work you'll need to be on the 6.1.2 Build at least. Upgrading from a 6.0 Installation is not supported because you will run into problems. See the [Release Notes](https://t.co/3NRHCLZbOS) for further details.status: corpus: 267 alsoLike: - {ref: posts/announcing-end-of-support-life-for-vsphere-7-0, score: 1.00} - {ref: posts/hpe-vm-essentials-part-2, score: 1.00} - {ref: solutions/vmware/vsphere-foundation, score: 0.59}
{ "apiVersion": "soultec.ch/v1", "kind": "Post", "metadata": { "name": "vmware-releases-6-5-update-1", "locale": "en", "labels": { "author": "dario-doerflinger", "capability/virtualization": "1.37", "vendor/vmware": "0.88" }, "annotations": { "source": "blog-content/posts/en/vmware-releases-6-5-update-1.md", "route": "/en/insights/vmware-releases-6-5-update-1/", "schema": "/nerd/schema/posts.json", "markdown": "/en/insights/vmware-releases-6-5-update-1.md" } }, "spec": { "title": "vSphere 6.5 Update 1", "date": "2017-07-31", "author": "dario-doerflinger", "locale": "en", "summary": "A couple of days ago VMware released version 6.5 Update 1 for some of their products: vCenter Server: Link ESXi: Link, Link to HPE Custom Image Site Recovery Manager (SRM): Link I was waiting for", "capabilities": [ "virtualization" ], "vendors": [ "vmware" ], "legacySlug": "vmware-releases-6-5-update-1", "migrated": "2026-08-24", "draft": false }, "sections": [ { "body": "A couple of days ago VMware released version 6.5 Update 1 for some of their products:\n\n- vCenter Server: [Link](https://my.vmware.com/group/vmware/details?downloadGroup=VC65U1&productId=614&rPId=17343)\n- ESXi: [Link](https://my.vmware.com/group/vmware/details?downloadGroup=ESXI65U1&productId=614&rPId=17343), [Link to HPE Custom Image](https://my.vmware.com/group/vmware/details?downloadGroup=OEM-ESXI65U1-HPE&productId=614)\n- Site Recovery Manager (SRM): [Link](https://my.vmware.com/group/vmware/details?downloadGroup=SRM651&productId=617&rPId=17333)\n\nI was waiting for Update 1 of the vSphere Stack for a while now, and the List of bugfixes has quite a few entries with critical bug fixes." }, { "heading": "

Installation Update 1 on 6.5 VCSA

",
"body": "The Update process is incredibly fast. Attach the .iso to your VCSA VM. Go the VAMI (https://<your-vcenter>:5480) and select the Update Tab. Choose to check for Updates on CD-ROM and then install the updates.\n\nAfter about 4 minutes the installation is done and you'll need to manually reboot the appliance. That's it you're done.\n\nUpgrading from vSphere 6.0 Update 3 is now fully supported with 6.5 Update 1." }, { "heading": "

Upgrading ESXi hosts to 6.5 Update 1

",
"body": "With ESXi hosts there are many roads to choose from.\n\n- Patch using VMware Update Manager\n- Upgrade using VMware Update Manager (Upload the iso file)\n- Re-Install using the latest image and kickstart script\n\nIn my Lab where we still use HPE G7 hardware (I know, it's not supported, but it still works and it's a lab..) I had a couple of problems. Using the iso with VUM did not work. Next I got a purple screen when doing a fresh install with the latest HPE Image (see link above). The exception was of type 14 (seems to be a page fault according to VMware KBs) so I'm not sure if it's because the hardware is not supported anymore or if I have some hardware issues.\n\nAnyways, I'll be working on that and I'm sure I'll get it to work and update my findings here." }, { "heading": "

Upgrading SRM to 6.5 Update 1

",
"body": "For this upgrade to work you'll need to be on the 6.1.2 Build at least. Upgrading from a 6.0 Installation is not supported because you will run into problems. See the [Release Notes](https://t.co/3NRHCLZbOS) for further details." } ], "status": { "corpus": 267, "alsoLike": [ { "ref": "posts/announcing-end-of-support-life-for-vsphere-7-0", "score": "1.00" }, { "ref": "posts/hpe-vm-essentials-part-2", "score": "1.00" }, { "ref": "solutions/vmware/vsphere-foundation", "score": "0.59" } ] }}
apiVersion = "soultec.ch/v1"kind = "Post"[metadata]name = "vmware-releases-6-5-update-1"locale = "en"[metadata.labels]author = "dario-doerflinger""capability/virtualization" = "1.37""vendor/vmware" = "0.88"[metadata.annotations]source = "blog-content/posts/en/vmware-releases-6-5-update-1.md"route = "/en/insights/vmware-releases-6-5-update-1/"schema = "/nerd/schema/posts.json"markdown = "/en/insights/vmware-releases-6-5-update-1.md"[spec]title = "vSphere 6.5 Update 1"date = 2017-07-31author = "dario-doerflinger"locale = "en"summary = "A couple of days ago VMware released version 6.5 Update 1 for some of their products: vCenter Server: Link ESXi: Link, Link to HPE Custom Image Site Recovery Manager (SRM): Link I was waiting for"capabilities = ["virtualization"]vendors = ["vmware"]legacySlug = "vmware-releases-6-5-update-1"migrated = 2026-08-24draft = false[[sections]]body = '''A couple of days ago VMware released version 6.5 Update 1 for some of their products:- vCenter Server: [Link](https://my.vmware.com/group/vmware/details?downloadGroup=VC65U1&productId=614&rPId=17343)- ESXi: [Link](https://my.vmware.com/group/vmware/details?downloadGroup=ESXI65U1&productId=614&rPId=17343), [Link to HPE Custom Image](https://my.vmware.com/group/vmware/details?downloadGroup=OEM-ESXI65U1-HPE&productId=614)- Site Recovery Manager (SRM): [Link](https://my.vmware.com/group/vmware/details?downloadGroup=SRM651&productId=617&rPId=17333)I was waiting for Update 1 of the vSphere Stack for a while now, and the List of bugfixes has quite a few entries with critical bug fixes.'''[[sections]]heading = "

Installation Update 1 on 6.5 VCSA

"
body = '''The Update process is incredibly fast. Attach the .iso to your VCSA VM. Go the VAMI (https://<your-vcenter>:5480) and select the Update Tab. Choose to check for Updates on CD-ROM and then install the updates.After about 4 minutes the installation is done and you'll need to manually reboot the appliance. That's it you're done.Upgrading from vSphere 6.0 Update 3 is now fully supported with 6.5 Update 1.'''[[sections]]heading = "

Upgrading ESXi hosts to 6.5 Update 1

"
body = '''With ESXi hosts there are many roads to choose from.- Patch using VMware Update Manager- Upgrade using VMware Update Manager (Upload the iso file)- Re-Install using the latest image and kickstart scriptIn my Lab where we still use HPE G7 hardware (I know, it's not supported, but it still works and it's a lab..) I had a couple of problems. Using the iso with VUM did not work. Next I got a purple screen when doing a fresh install with the latest HPE Image (see link above). The exception was of type 14 (seems to be a page fault according to VMware KBs) so I'm not sure if it's because the hardware is not supported anymore or if I have some hardware issues.Anyways, I'll be working on that and I'm sure I'll get it to work and update my findings here.'''[[sections]]heading = "

Upgrading SRM to 6.5 Update 1

"
body = "For this upgrade to work you'll need to be on the 6.1.2 Build at least. Upgrading from a 6.0 Installation is not supported because you will run into problems. See the [Release Notes](https://t.co/3NRHCLZbOS) for further details."[status]corpus = 267[[status.alsoLike]]ref = "posts/announcing-end-of-support-life-for-vsphere-7-0"score = "1.00"[[status.alsoLike]]ref = "posts/hpe-vm-essentials-part-2"score = "1.00"[[status.alsoLike]]ref = "solutions/vmware/vsphere-foundation"score = "0.59"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Post"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>vmware-releases-6-5-update-1</name> <locale>en</locale> <labels> <author>dario-doerflinger</author> <entry key="capability/virtualization">1.37</entry> <entry key="vendor/vmware">0.88</entry> </labels> <annotations> <source>blog-content/posts/en/vmware-releases-6-5-update-1.md</source> <route>/en/insights/vmware-releases-6-5-update-1/</route> <schema>/nerd/schema/posts.json</schema> <markdown>/en/insights/vmware-releases-6-5-update-1.md</markdown> </annotations> </metadata> <spec> <title>vSphere 6.5 Update 1</title> <date>2017-07-31</date> <author>dario-doerflinger</author> <locale>en</locale> <summary>A couple of days ago VMware released version 6.5 Update 1 for some of their products: vCenter Server: Link ESXi: Link, Link to HPE Custom Image Site Recovery Manager (SRM): Link I was waiting for</summary> <capabilities> <item>virtualization</item> </capabilities> <vendors> <item>vmware</item> </vendors> <legacySlug>vmware-releases-6-5-update-1</legacySlug> <migrated>2026-08-24</migrated> <draft>false</draft> </spec> <sections> <section> <body>A couple of days ago VMware released version 6.5 Update 1 for some of their products:- vCenter Server: [Link](https://my.vmware.com/group/vmware/details?downloadGroup=VC65U1&amp;productId=614&amp;rPId=17343)- ESXi: [Link](https://my.vmware.com/group/vmware/details?downloadGroup=ESXI65U1&amp;productId=614&amp;rPId=17343), [Link to HPE Custom Image](https://my.vmware.com/group/vmware/details?downloadGroup=OEM-ESXI65U1-HPE&amp;productId=614)- Site Recovery Manager (SRM): [Link](https://my.vmware.com/group/vmware/details?downloadGroup=SRM651&amp;productId=617&amp;rPId=17333)I was waiting for Update 1 of the vSphere Stack for a while now, and the List of bugfixes has quite a few entries with critical bug fixes. </body> </section> <section> <heading>

Installation Update 1 on 6.5 VCSA

</heading>
<body>The Update process is incredibly fast. Attach the .iso to your VCSA VM. Go the VAMI (https://&lt;your-vcenter&gt;:5480) and select the Update Tab. Choose to check for Updates on CD-ROM and then install the updates.After about 4 minutes the installation is done and you'll need to manually reboot the appliance. That's it you're done.Upgrading from vSphere 6.0 Update 3 is now fully supported with 6.5 Update 1. </body> </section> <section> <heading>

Upgrading ESXi hosts to 6.5 Update 1

</heading>
<body>With ESXi hosts there are many roads to choose from.- Patch using VMware Update Manager- Upgrade using VMware Update Manager (Upload the iso file)- Re-Install using the latest image and kickstart scriptIn my Lab where we still use HPE G7 hardware (I know, it's not supported, but it still works and it's a lab..) I had a couple of problems. Using the iso with VUM did not work. Next I got a purple screen when doing a fresh install with the latest HPE Image (see link above). The exception was of type 14 (seems to be a page fault according to VMware KBs) so I'm not sure if it's because the hardware is not supported anymore or if I have some hardware issues.Anyways, I'll be working on that and I'm sure I'll get it to work and update my findings here. </body> </section> <section> <heading>

Upgrading SRM to 6.5 Update 1

</heading>
<body>For this upgrade to work you'll need to be on the 6.1.2 Build at least. Upgrading from a 6.0 Installation is not supported because you will run into problems. See the [Release Notes](https://t.co/3NRHCLZbOS) for further details.</body> </section> </sections> <status> <corpus>267</corpus> <alsoLike> <item> <ref>posts/announcing-end-of-support-life-for-vsphere-7-0</ref> <score>1.00</score> </item> <item> <ref>posts/hpe-vm-essentials-part-2</ref> <score>1.00</score> </item> <item> <ref>solutions/vmware/vsphere-foundation</ref> <score>0.59</score> </item> </alsoLike> </status></manifest>
Post · 2017-07-31

vSphere 6.5 Update 1

A couple of days ago VMware released version 6.5 Update 1 for some of their products: vCenter Server: Link ESXi: Link, Link to HPE Custom Image Site Recovery Manager (SRM): Link I was waiting for

2017-07-31Date
Dario DörflingerAuthor
2Min read
Topics Virtualization 1.37
Vendors VMware 0.88

This post is from 2017. It stays online because people still look for it, but it describes the products as they were then.

A couple of days ago VMware released version 6.5 Update 1 for some of their products:

I was waiting for Update 1 of the vSphere Stack for a while now, and the List of bugfixes has quite a few entries with critical bug fixes.

Installation Update 1 on 6.5 VCSA

The Update process is incredibly fast. Attach the .iso to your VCSA VM. Go the VAMI (https://:5480) and select the Update Tab. Choose to check for Updates on CD-ROM and then install the updates.

After about 4 minutes the installation is done and you’ll need to manually reboot the appliance. That’s it you’re done.

Upgrading from vSphere 6.0 Update 3 is now fully supported with 6.5 Update 1.

Upgrading ESXi hosts to 6.5 Update 1

With ESXi hosts there are many roads to choose from.

  • Patch using VMware Update Manager
  • Upgrade using VMware Update Manager (Upload the iso file)
  • Re-Install using the latest image and kickstart script

In my Lab where we still use HPE G7 hardware (I know, it’s not supported, but it still works and it’s a lab..) I had a couple of problems. Using the iso with VUM did not work. Next I got a purple screen when doing a fresh install with the latest HPE Image (see link above). The exception was of type 14 (seems to be a page fault according to VMware KBs) so I’m not sure if it’s because the hardware is not supported anymore or if I have some hardware issues.

Anyways, I’ll be working on that and I’m sure I’ll get it to work and update my findings here.

Upgrading SRM to 6.5 Update 1

For this upgrade to work you’ll need to be on the 6.1.2 Build at least. Upgrading from a 6.0 Installation is not supported because you will run into problems. See the Release Notes for further details.

You might also like