Dear Community Guru's.

I've found posts as old as 7 years old referring to this issue, and I'm having the exact problem now in 2019. I get the errors below in the event viewer each time I plug in our out a USB device. And also at random times ( without actually plugging in anything.)

I'm running VMware Workstation 15 pro, latest version as of today ( 15.0.2 build-10952284 ), on an ASUS ROG GL702V Notebook, on Windows 10 64 bits latest build (17763).

Reading in ASUS' forums, the only solution that actually works is to disable the "VMWare USB Arbitration Service" , but that is not a real solution since it disables the possibility to attach USB devices to VM's.

Any ideas/suggestions?

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\PnpManager).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32111</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\PnpManager</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

 

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\nxusbh).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32110</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\nxusbh</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

 

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\nxusbf).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32109</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\nxusbf</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

I tried registering to the latest vSphere available version, but when I click the button, the following message appears:

hi guys,

i don't know if i'm right here. I have a problem with my hauppauge WinTV-dualHD dvb-c tuner.

I use a vmware esxi 6.7 host (6.7.0 Update 1 (Build 13004448)) and a vm with ubuntu 18.04.2 (open-vm-tools 10.3.0 build 8931395). I use a USB 3 and a USB 2 controller in the VM - same problem.

I configure the vm with the usb device and i can see this device in my vm. I installed the drivers via ppa from hauppauge and tvheadend.

The strange thing is that i can see the usb-tuners and configure them, but the tv-channel scan can't find something (but the tuner led is blinking - whats is right). in tvheadend the bandwidth is 0 - that is not correct. maybe there are some usb parameters - i can't find a list or somethink like that with the parameters and there meanings.

i use the same config on a native ubuntu server system with the same install and config - there are no problems.

i know it's a not supportet device, but maybe you can help me? =)

best regards
trayntab

I downloaded the Windows 10 1809 and Server 2019 ISOs the day they became available so I can start working on my templates.

I built the templates with EFI, paravirtual for the C drive and vmxnet3 adapter. I've been using this combo for other versions of windows 10/8/7and windows server 2008r2/2012r2/1016 without issue.

So far Windows 2019 (with desktop experience) seems to be ok at least for a basic vm and guest customization. Haven't tried anything else yet.

Windows 10 1809 on the other hand is very, very slow to reboot after the initial install or even just rebooting after making some changes post install. After installing the OS it took 10-15 minutes for the initial windows setup stuff (user, security settings, etc) to appear . I tried a VM set to BIOS and it seemed faster but was still quite slow. Server 2019 and other versions of windows 10 have no issue.

The hosts are esxi 6.5 and 6.7.

I haven't had a chance to try every combo of BIOS/EFI/vmxnet3/e1000e/paravirtual/lsi sas to see if one is the cause of the issue but was wondering if anyone else had noticed any issues or if it was just me?

Thanks

1. I have a basic machine blueprint (win2016 vsphere machine type) defined in my catalog.

2. I have created a custom vRO action that consists of the following javascript code:

var roles = new Array();
roles = System.getModule("com.vmware.o11n.plugin.chef.helpers").getRunlistCandidates(host);
System.log(host);
System.log(roles);
return roles;

It is calling an action supplied by the chef plugin and passing in the chef host, and returns a string array of chef roles, cookbook recipes.

3. I have created a new property definition named roles, defined it as type string, required, drop down, with external values, pointing it to the action, and populating the host value:

When I click select to choose the Script action, a new window pops up and I get the vRO tree populated showing my custom action and the chef plugin helper action successfully. I can choose either or and populate the value of the host without issue.

4. When I request the blueprint, I get the following error once the fields on the request form complete loading:

Unable to start action 'com.caresource.devopstransformation/getRunListCall'. Reason 'Action 'getRunListCall' in module 'com.caresource.devopstransformation' failed : type Cannot be null".

The drop down is empty. All other fields on the request are active and populate successfully.

Troubleshooting:

I can put the very same action in a vRO workflow and when I run it, I choose the host value based on the chef plugin and it completes successfully, printing out the host and the chef roles/run lists/cookbook/recipes in the log.

I can put the chef action my custom action is calling in a workflow and execute it successfully without issue.

I can point the property definition to the chef action, set the host to be the same, and it fails during the request with the same error.

Unable to start action 'com.vmware.o11n.plugin.chef.helpers/getRunlistCandidates'. Reason 'Action 'getRunlistCandidates' in module 'com.vmware.o11n.plugin.chef.helpers' failed : type Cannot be null'.

I can create a XaaS blueprint that executes the workflow that calls both of these actions and it completes fine without any errors.

And what version is that?

And how do I find it?

Cheers

We have a small View environment with around 80 linked clone vms. We are looking to expand to our DR facility as well. The plan is to have enough compute and storage at each location to provide enough in case either site fails. But we don't want DR just sitting. I created a Pod for DR and did a round robin DNS record (since we are only do local connections) to hit either a connection server at main or dr (4 in total 2 at each site) Everything is working fine, but since the connection server that a user will connect to is random (and we want it that way), if we need to do any management with that user, we have to log into a connection that the user is logged into and since we have two pods, we have to log into both to find the user. Is there anyway to log into one and see all logged in users? If we log into a connection server, we can only see the users that are connected to that pod.

Hello I am facing the problem that Vmware workstation Device/Credential guard are not compatible. Vmware will run after disabling the device/credential guard.
Even my device/credential guard is already disabled HYper-V function is also unchecked
Please help me

This problem is facing after updating my windows 10 Pro to 1803 Version (April Update)

Thank You!!!

Author : jacquiew

URL : http:////docs.vmware.com/en/VMware-Horizon-Client-for-Windows/4.4/com.vmware.horizon.windows-client-44-doc/GUID-F19EBDF6-20A3-4A8B-95AE-786CC74F26AF.html

Topic Name : Microsoft Windows Installer Command-Line Options

Publication Name : Using VMware Horizon Client for Windows

Product/Version : VMware Horizon Client for Windows/4.4

Question :

When I try to install, either remotely or via the command line on the local computer, none of the command line options are recognized.  If I run the .exe /s it runs the exact same installation as if I run .exe /s /v"all of my msi options".  It reboots when I tell it not to, doesn't set the default server, and doesn't save a log file where I tell it to.

Hello,

we are currently evaluation vCD. We are a bit confused what's VMware strategy if it comes to billing / usage reporting.

There are a lot of differenty ways (vCenter Chargeback, vRealize Business, vROPs PlugIn...) and no one seems to be the golden way.

Our requirement is to gerenate usage reports for each org / org vdc.

We don't need different pricing models because this will be done in our ERP software.

We'd like to report only the usage of the customers based on "service offerings

Possible service offerings

"1GB RAM/hour in PVDC A"

"VPN Uptime/hour in PVDC B"

"Flash Storage used GB/hour im PVDC C"

...

...

What would be the best solution for this requirement?

Kidn Regards,

Marcel

Hi Everyone

Very new to this site.

We have inherited a client that has VMware ESXi 6.5 U2 installed on a Kingston USB 3 thumb drive.

We have encountered an issue where once the host was restarted ESX failed to boot with several files

Fatal Error 33 (Inconsistent Data)

I replaced these files and managed to get the server to boot.

However, would like to replace the USB and reload ESX onto the USB

My question is around transferring the configuration to the USB from the existing USB?

Regards

Matt

HI ,

Just curious on how everyone is assigning their App Stacks .  I see pro's and con's both ways.

Right now we have One A/D Group assigned to each App Stack and place users in that A/D group .

Only thing we don't like is - there doesn't seem a way via Group Assigning to Immediately give the user the app w/ out a reboot.

Whereas assigning the app stack directly to a User and not a group would allow that.

We are leaning towards Individual assigns via App Stack.. however run into questions on upgrades of App stacks .

Let's say your updating Chrome.. you have 1000 users assigned to 'old Chrome .

You click UPDATE on the 'old' chrome.. hop on an install machine and update it .

Now App Volumes just created a whole new App Stack called 'new' Chrome.  However NO user assigns followed to the 'new' chrome. ( i Get it.. one needs to test it..etc before giving it to everyone )

Assuming we are assigning each app directly to users.. How to I transfer the 1000 people from 'old' chrome to 'new' chrome ?

Is direct assign to users not feasible and we're stuck using A/D group assigning ?

thanks !

I have a esxi 6.7.0 Update 1 (Build 10302608)，when I create a new windows server2016 Standard Edition，at the end of the install, the system restart and dispaly the Login interface,need press ctrl+alt+del to login,I use ctrl+alt+insert，click the esxi menu sent "ctrl+alt+del" to windows server2016,but there is no response,still let me to press ctrl+alt+del to login,I try to reintall windows server2016 Standard Edition,and used diffent edition,even intall windows server2019,still the same problem can not login,still ask me to press ctrl+alt+del to login, I pressed ctrl+alt+insert，click the esxi menu sent "ctrl+alt+del" to windows serve,still  no response.

Please help me to see what is the reason and how to solve this problem. Thank you.

Hello Vmware community;

I have concluded that windows sandbox does not work with VMware workstation in windows 10 build 18329.1.  Enabling windows sandbox also enables windows defender credential guard features which causes the following error when trying to power on a virtual machine in vmware:

"VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard."

Upon searching you will find Vmware Knowledge Base Article 2146361 which references a link to the following Microsoft KB article:

Manage Windows Defender Credential Guard (Windows 10) | Microsoft Docs

Neither document mentions that the windows sandbox feature enables credential guard features.  Here is how to disable credential guard after uninstalling windows sandbox: https://kb.vmware.com/s/article/2146361

1. Hit the windows key+s for "Search" and type "windows security settings" and press enter. Navigate to:

Windows Security -->> Device Security -->> Core Isolation -->> Memory Integrity -->> Select Off

2. Hit the windows key+r for "Run" and type "gpedit.msc" and press enter. Navigate to:

Local Computer Policy ->> Computer Configuration ->> Administrative Templates ->> System - Device Guard ->> Turn on Virtualization

Double click that .... and select "Disable" ...

3. Go to Control Panel ->> Uninstall a Program ->> Turn Windows features on or off ->> (uncheck/turn off): Hyper-V & Windows Sandbox.

*Click OK

*Select Do not restart.

4. Type the following cmds in cmd prompt.. to Delete the related EFI variables from the BCD file...

Launch cmd as administrator...

bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader

bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"

bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}

bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS

bcdedit /set hypervisorlaunchtype off

5. Restart your system ...

This howto has been kinda, sort of covered in various internet searches.  But no one seems to detail clearly how windows sandbox enables windows defender credential guard.  I found this out upgrading to window 10 build 18329.1. I hope this thread is helpful to someone.

下記のページを見てESXiのバックアップとリストアの検証を行っております。

VMware Knowledge Base

バックアップは問題なく実施出来たのですが、

リストア時は以下のエラーが出力され失敗してしまいます。

PS C:\WINDOWS\system32> Set-VMHostFirmware -VMHost 192.168.2.231 -Restore -SourcePath C:\Log\configBundle-192.168.2.231.

tgz -HostUser root -HostPassword password

Set-VMHostFirmware : 2019/04/01 18:32:53        Set-VMHostFirmware              The operation is not allowed in the current state.

発生場所 行:1 文字:1

+ Set-VMHostFirmware -VMHost 192.168.2.231 -Restore -SourcePath C:\Log\ ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Set-VMHostFirmware], InvalidState

    + FullyQualifiedErrorId : Client20_SystemManagementServiceImpl_RestoreVmHostFirmware_ViError,VMware.VimAutomation.

   ViCore.Cmdlets.Commands.Host.SetVMHostFirmware

VMHost               UploadUrl

------               ---------

192.168.2.231        http://192.168.2.231/tmp/configBundle.tgz

PS C:\WINDOWS\system32>

※メンテナンスモードの状態です。

アドバイスを頂けないでしょうか。

Hey all,

I have a VM that doesn't want to auto-start with the host. There are four other VMs on the same host that autostart without issue, and the only difference I can find between them all is that the problem VM has SATA passthrough configured for a 5TB drive.

Host: Dell PowerEdge R310

• 4 CPUs x Intel Xeon CPU X3430 @ 2.40 GHz
• 32GB RAM

ESXi Version: 6.5.0 (Build 4564106)

• Image profile: Dell-ESXi-6.5.0-4564106-A00 (Dell)
• Free vSphere 6 Hypervisor license

Overall VM Environment: 5 ESXi 6.5 Linux VMs

• Each running Ubuntu 18.04.1 LTS (x64)
• No HA

Problem VM Configuration:

• 4 vCPUs
• 16GB RAM
• 450GB vmdk
• 4.55TB passthrough vmdk

I've set the problem VM to the lowest priority autostart in the hopes that maybe it's timing related, but the issue remains. I've also noticed that after ESXi shuts down and starts up again, the Recent Tasks window shows the problem VM starting first, then a Refresh Network System, then the other VMs all start up...

If I start the problem VM manually, it fires up with no issues.

The SATA passthrough was set up with help from this article: How to passthrough SATA drives directly on VMWare ESXI 6.5 as RDMs · GitHub

I can provide whatever log files are desired, if needed. Thanks in advance to anyone who might have some answers!

Best regards,

Ted

以下のコマンドでPowerCLIの出力をCSVにすると読めない文字になります。

【コマンド】

PS C:\WINDOWS\system32> $global:DefaultVIServers | Get-AdvancedSetting | Format-Table -Autosize -Wrap | Export-Csv -Encoding UTF8 -NoTypeInformation -Path C:\work\Exppppp.csv

PS C:\WINDOWS\system32> $global:DefaultVIServers | Get-AdvancedSetting | Format-Table -Autosize -Wrap | Export-Csv -Encoding Unicode -NoTypeInformation -Path C:\work\Exppppp.csv

PS C:\WINDOWS\system32> $global:DefaultVIServers | Get-AdvancedSetting | Format-Table -Autosize -Wrap | Export-Csv -Encoding Default -NoTypeInformation -Path C:\work\Exppppp.csv

【Exppppp.csv】※一部抜粋

"ClassId2e4f51ef21dd47e99d3c952918aff9cd","pageHeaderEntry","pageFooterEntry","autosizeInfo","shapeInfo","groupingEntry"

"033ecb2bc07a4d43b5ef94ed5a35d280",,,"Microsoft.PowerShell.Commands.Internal.Format.AutosizeInfo","Microsoft.PowerShell.Commands.Internal.Format.TableHeaderInfo",

"9e210fe47d09416682b841769c78b8a3",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

"27c87ef9bbda4f709f6b4002fa4af63c",,,,,

解決方法をご教示頂けないでしょうか。

After having upgraded to VMware Workstation 15 on my Windows 10x64 machine, each of my VMs shows a black flicker from time to time (once every 10 minutes or so).

This disturbance can be reproduced easily:

Simply start a VM with a Windows 10x64 OS installed and wait for about 10 seconds after having signed in to the guest OS. Then the first black flicker will occur:

After having opened a support ticket I'm having long discussions with VMware Support. They don't seem to be able to reproduce this issue.

So I'm asking here: Can anyone reproduce this issue?

I am unsure if this has been addressed before--if so I was not able to find much on the topic.

I am deploying new parent images with Windows 10 1809 to get us off our current Win7 environment. As part of our development process we are trying to get our logon times down. Currently using Persona with a decent sized profile, we are seeing logon reach about 1min plus some change. This is about a 30 second increase from the current logon time in our Win7 Production environment.

Onto the issue.....we have installed Horizon agent 7.7 on the parent image and enabled the Horizon View Logon Monitor service(the Logon monitor in bundled into the agent after version 7.5 I believe). However, after casting this image out to a test pool, the logs (located: C:\ProgramData\VMware\VMware Logon Monitor\Logs)are not showing almost any of the information that is promised in this article. It is mostly just gibberish in the main log, and the session log file itself is just MIA.

Has the Logon Monitor been deprecated? Or is it no longer being supported?

It seems like a tool that would be very useful to have when troubleshooting the logon time issues, without it we are flying blind trying to determine where the issues may be.

i deployed a nsx-t 2.4 manager on KVM with "medium" type, it worked just fine until i installed second manager(on another KVM host) and join it to the first one.

they all display the following messages on the web browser after i type in the admin account and password to login, as shown below:

i could not figure out why this error happen and it just can't be fixed after i restart services such as "ui-service" in the manager or even reboot the manager.

does anyone know why? the "manager.log" and "syslog" in the manager appliance did not show messages which is truly helpful.