Reply to thread

Message

<blockquote data-quote="simmerskool" data-source="post: 1039604" data-attributes="member: 61091"><p>FIXED <img class="smilie smilie--emoji" loading="lazy" alt="😁" title="Beaming face with smiling eyes&nbsp; &nbsp; :grin:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f601.png" data-shortname=":grin:" /><img class="smilie smilie--emoji" loading="lazy" alt="🥳" title="Partying face&nbsp; &nbsp; :partying_face:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f973.png" data-shortname=":partying_face:" /> concern for naught! Consensus (&amp; VMw support too) was uninstall VMware 16.2.5 &amp; reinstall. Used win10 add remove, uninstall was grayed out(?) <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite132" alt=":unsure:" title="Unsure&nbsp; &nbsp; :unsure:" loading="lazy" data-shortname=":unsure:" />...but it offered Modify, which gave me the 3 options including Repair, tried repair 1st, it ran and fixed the &quot;broken bits&quot; left in the aftermath of the MS win10 in-place upgrade from .iso performed to fix Windows Defender Firewall and its Service. VMware repaired its virtual network drivers, and whatever else... forced reboot, and ALL GOOD <img class="smilie smilie--emoji" loading="lazy" alt="😆" title="Grinning squinting face&nbsp; &nbsp; :laughing:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f606.png" data-shortname=":laughing:" /> Big thanks to everyone including those who helped with the firewall snafu. (VMware was not the cause of the win firewall issue -- never thought it was)</p></blockquote><p></p>

[QUOTE="simmerskool, post: 1039604, member: 61091"] FIXED 😁🥳 concern for naught! Consensus (& VMw support too) was uninstall VMware 16.2.5 & reinstall. Used win10 add remove, uninstall was grayed out(?) :unsure:...but it offered Modify, which gave me the 3 options including Repair, tried repair 1st, it ran and fixed the "broken bits" left in the aftermath of the MS win10 in-place upgrade from .iso performed to fix Windows Defender Firewall and its Service. VMware repaired its virtual network drivers, and whatever else... forced reboot, and ALL GOOD 😆 Big thanks to everyone including those who helped with the firewall snafu. (VMware was not the cause of the win firewall issue -- never thought it was) [/QUOTE]

Verification