- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When loading Intel vPro Technology Module for Windows PowerShell v16.0.5.1, the following error is displayed:
At C:\Program Files\Intel\IntelvProModule_16.0.5.1\Bin\IntelvPro\Invoke-AMTGUI.ps1:353 char:47
+ for ($i=0; $i -le $properties.Length � 1; $i+=2)
+ ~~~
There is a corrupt character between $properties.Length and 1; on line 353 in the file Invoke-AMTGUI.ps1
In a hex editor the character is shown as EF BF BD
In a previous version (IntelvProModule_16.0.0.5), that line is displayed in a text editor as:
for ($i=0; $i -le $properties.Length – 1; $i+=2)
That makes it look like a minus sign (-). However when viewing that version in a hex editor, the character is show as 96. ANSI character 0x96 is actually an En Dash.
I'm assuming this is supposed to be a minus sign? (which would be 0x2D)
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, ICIT,
I hope this email finds you well.
Please give me time to review the issue and perform some tests; I will provide an update in the coming days.
Regards,
Miguel C.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, ICIT,
I hope you're doing well.
After doing some tests, the development team determined this is an erratum and will be fixed in the next release of the vPro Module for PowerShell.
In the meantime, you can directly edit the module on line 353 and replace the characters with a hyphen and it will work.
We will gladly provide further assistance if necessary.
Regards,
Miguel C.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, ICIT,
I am following up on the case and wondering if you have been able to run our workaround. Your feedback will be appreciated.
Regards,
Miguel C.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the workaround is working.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, ICIT,
Thank you for your quick response.
I am glad to know the workaround fixed the issue. Do not hesitate to reply if further assistance is necessary.
Regards,
Miguel C.
Intel Customer Support Technician

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page