Accessing USB device in Windows 10 Tech Preview under Hyper-v

I am using Windows 10 Technical Preview in a VM created with Hyper-V on a Windows 8.1 machine, and accessing the VM with Remote Desktop Connection. In RDC, I have set the local resources to include ports and "other PnP devices," but I still
cannot see my USB Microsoft LifeCam. The camera works fine on the host, but in Windows 10 I get a message that says, "To get started, connect a camera."
What setting do I need to change in order to access this device in the VM?
Thanks!
MW

Hi,
Since USB drive could be work properly, VM and RDP settings should be ok. For this problem, it is probably a driver compatibility problem, it would be better to contact LifeCam support to confirm the problem:
http://www.microsoft.com/hardware/en-in/support/contact-us
Roger Lu
TechNet Community Support

Similar Messages

About the error: "The account is not authorized to login from this station" when you access NAS devices from Windows 10 Technical Preview (build 9926)

Scenario:
With the release of Windows 10 Technical Preview (build 9926), some users may encounter an error message of “The account is not authorized to login from this station” when trying to access remote files saved in NAS storage. In
addition, the following error log may also be found via Event Viewer:
Rejected an insecure guest logon.
This event indicates that the server attempted to log the user on as an unauthenticated guest but was denied by the client. Guest logons do not support standard security features such as signing and encryption. As a result,
guest logons are vulnerable to man-in-the-middle attacks that can expose sensitive data on the network. Windows disables insecure guest logons by default. Microsoft does not recommend enabling insecure guest logons.
Background:
The error message is due to a change we made in Windows 10 Technical Preview (build 9926) which is related to security and remote file access that may affect you.
Previously, remote file access includes a way of connecting to a file server without a username and password, which was termed as “guest access”.
With guest access authentication, the user does not need to send a user name or password.
The security change is intended to address a weakness when using guest access. While the server may be fine not distinguishing among clients for files (and, you can imagine in the home scenario that it doesn’t
matter to you which of your family members is looking at the shared folder of pictures from your last vacation), this can actually put you at risk elsewhere. Without an account and password, the client doesn’t end up with a secure connection to the server.
A malicious server can put itself in the middle (also known as the Man-In-The-Middle attack), and trick the client into sending files or accepting malicious data. This is not necessarily a big concern in your home, but can be an issue when you take your
laptop to your local coffee shop and someone there is lurking, ready to compromise your automatic connections to a server that you can’t verify. Or when your child goes back to the dorm at the university. The change we made removes the ability to connect
to NAS devices with guest access, but the error message which is shown in build 9926 does not clearly explain what happened. We are working on a better experience for the final product which will help people who are in this situation.
As a Windows Insider you’re seeing our work in progress; we’re sorry for any inconvenience it may have caused.
Suggestion:
You may see some workarounds (eg. making a registry change restores your ability to connect with guest access).
We do NOT recommend making that change as it leaves you vulnerable to the kinds of attacks this change was meant to protect you from.
The recommended solution is to add an explicit account and password on your NAS device, and use that for the connections. It is a one-time inconvenience,
but the long term benefits are worthwhile. If you are having trouble configuring your system, send us your feedback via the Feedback App and post your information here so we can document additional affected scenarios.
Alex Zhao
TechNet Community Support

Hi RPMM,
Homegroup works great in Windows 10 Technical Preview (9926 build), when I invited my Windows 10 Technical Preview (9926 build) joined in HomeGroup, I can access the shares smoothly:
My shares settings is like this:
Alex Zhao
TechNet Community Support

HDMI Audio doesn't work on Windows 10 Tech Preview

I am using a HP ENVY TouchSmart 15-j053cl Notebook PC and often plug it directly into my television for streaming video. However, after updating to windows 10 tech preview the HDMI output for audio no longer appears in playback devices, though video is fine. Upon further inspection I found that the device is not starting via device manager, i.e
"This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful."
I attempted to reinstall the driver from the support site for windows 8.1, but that had no effect. The driver I installed
IDT High-Definition (HD) Audio Driver 2013-09-30 , Version6.10.6491.0, 43.95M
Located http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4158&lc=en&cc=us&dlc=en&sw_lang=&product=5390...
Are there any drivers out yet that can bridge the gap from 8.1 to 10?
Any help would be great,
Coletrain

@Coletrain
Thank you for using HP support forum. I have sent you a private message. If you’re unsure how to check your private messages please click here.
Thank you,
Omar
I Work for HP

Crypto failure when upgrading Windows 8.1 Pro install to Windows 10 Tech Preview 10041

Has anybody experienced the following error when trying to upgrade a Windows 8.1 Pro install to Windows 10 Tech Preview 10041
crypto_self_test_failed
The system reboots twice both times with the same error and then reverts back to Windows 8.1 Pro. This occurs during the upgrade process. Windows 10 never installs.
Thoughts? Suggestions?
Thanks
Eric Sten

Hi Eric,
It seems to be the upgrade self-test fails.
For testing Windows 10, you may consider take use of Hyper-V and install a VM of Windows 10:
Step-By-Step: Creating and Running A Windows 10 VM on Windows 8.1
Or try a dual boot:
How to Dual Boot Between Windows 7 (or Windows 8.1) and Windows 10 Technical
Preview (VHDX)
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Installing Windows 10 Tech Preview on Yoga 13 as dual boot

Hi guys,
I'm new here, but have the Yoga 13 for almost 2 years now.
But that's not the case though
I'm having problems installing the Windows 10 Technical Preview on my machine on a new partition. I have lowered the storage on my Windows8_OS drive with around 40GB. Got everything ready for install and got the Bios to boot from the USB. But when i'm about to choose the partition to install the Tech Preview, the button NEXT won't show. All I get is the message: "Windows cannot be installed on this disk. The selected disk is of the GPT partition style".
As this is the Lenovo Forums, I though you guys might know what causing the problem here.
Hope you guys know what I want and hopefully you have the answer.
Thanks in advance.
Details about my machine:
Processor: Intel i7
RAM: 8GB
Type system: 64-bits
SDD: 256GB
Solved!
Go to Solution.

Hi Bro,
I had the same problem, I am using lenovo ideapad yoga 13 with 128GB only. So you have more space.
Anyway, you have to follow the procedure by step by step.
1. Check your system properties about windows x86 or x64 and download the proper iso file in to your local directory.
http://windows.microsoft.com/en-gb/windows/preview-download?ocid=tp_site_downloadpage
Mine is a 64 bit version. So I downloaded x64.
2. Download rufus at below link
http://rufus.akeo.ie/
3. Then insert a thumb drive (at least 16GB) then choose GPT partition scheme and locate the disc image file.
4. Once you are done, restart the computer, go to bios (pressing F2), just check USB is set 1st boot device.
Then you will be able to install on your secondary partition.
Now I am posting this reply from W10-tech preview only. Wish you good luck. If still need more details, please feel to ask me. Thanks
Friendly
Cp

Can't attach USB devices in Windows XP Mode

I am still trying to set up my new Probook G1 450. It is presently in the original Win 7 Pro 64-bit OS.
I am trying to use Windows XP Mode. I can set up XP Mode, but I can't get USB access under it. But for me, the whole point of getting XP Mode is to be able to run two key programs which require USB access. The USB devices have been successfully installed in Win 7 (it's the programs that require XP Mode).
I have tried with VMLiteXPMode, Virtual Box, and finally with Windows Virtual PC. The results are about the same. I am presently trying Windox Virtual PC. When I access the USB button on the top of the XP Mode box, there is a list of all the USB devices. This looks like things are fine. All the devices are there. Hooray. Oops, too soon! It still doesn't work. One still has to "attach" the USB device, by clicking its listing under USB devices. When I do this, I get the following error message:
"Could not attach the USB device. You can attach the USB to a different USB port or restart the virtual machine and try again."
Yes, I can and have done all those things, and I get the same error message again and again and again. This is true for all USB devices (except the USB mouse, which works perfectly and automatically in XP mode and is *not* listed under USB):
* Epson Perfection scanner
* HP Laserject printer
* the computer's own HP HD Webcam,
and
* the computer's own Wireless/Bluetooth Device
For example, the scanner and printer will work well in the host machine, where I have installed them, but they can't be "attached" in XP Mode.
Notes:
* I have enabled "integration features"
* I have tried disconnecting and reconnecting the devices.
* If I try to install the printer in XP Mode, I can't do that, because this requires, at some point, the printer being plugged in to the USB. And I get the above error message when I try to attach it.
Also I have already had to deal with one driver issue (it came with the wrong driver for wireless; the right driver wasn't on the HP support page and couldn't be obtained by the computer's own "update' function), but when I finally discovered the right driver, wireless worked flawlessly
There is yet another possible driver issue, but I'll leave that for another topic later. One thing at a time.

@comvox
‎Thank you for using HP Support Forum. I have brought your issue to the appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message from an identified HP contact. Additionally, keep in mind not to publicly post ( serial numbers and case details).
If you are unfamiliar with the Forum's private messaging please click here to learn more.
Thank you,
Omar
I Work for HP

Unknown USB Device in Windows - VISA does not see it

Hello,
I'm trying to connect my STM microcontroller to my computer using USB protocol and VISA software. When I plug STM USB device into USB port Windows sees it as unknown device and can not find any driver for it. I assume that this is situation VISA was created for. So I want to use a driver wizard to create driver for this device, but VISA does not display it in a device list. I tried to create and install driver for my device as if it was not connected, and installed created driver manually but it did not work.
Is it possible that Windows detects a USB device and VISA can't see it?

It actually depends what sort of USB device it should be. If it is a COMM USB class device, Windows should be able to pick it up directly as serial port, if it is some proprietary USB class, then you either have to get a driver installed and access that driver somehow, or create an INF file with the VISA driver wizard for it and write the driver yourself in LabVIEW using the VISA USB Raw interface. Without a very good description of the low level USB protocol however this last option is a complete no go.
If the VISA driver wizard doesn't display the device in the list then Windows has already claimed it somehow.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Knowing when usb device ready (windows balloon window)

I have a device that when connected via USB, it will appear, then go away then reappear. When the device is finally ready, Windows pops up with its little balloon ready stating that its ready.
I am trying to access it but do not want to attempt until after it reappears, or when its ready. And a simple delay is not very reliable.
Is there a good way to detect if a USB device is "ready for use"?

Hello ngay528,
If you are doing this in CVI and you are using a VISA resource you can use the viFindRsrc command.
viFindRsrc:
Matches the value specified in Expression with all known instruments. On successful completion, the Return Count is the total number of matches and the Instrument Descriptor is the descriptor string for the first instrument that matches Expression. The Instrument Descriptor can be used to open an instrument with the viOpen operation. The Find Handle can be used in subsequent calls to the viFindNext operation to retrieve descriptor strings for the remaining instruments that were found.
This operation applies to VISA resource manager sessions only.
/*-------------------- Prototype ---------------------*/
ViStatus viFindRsrc (ViSession Rsrc_Manager_Handle,
   ViString Expression,
   ViPFindList Find_Handle,
   ViPUInt32 Return_Count,
   char Instrument_Descriptor[]);
Matches the value specified in Expression with all known instruments. On successful completion, the Return Count is the total number of matches and the Instrument Descriptor is the descriptor string for the first instrument that matches Expression. The Instrument Descriptor can be used to open an instrument with the viOpen operation. The Find Handle can be used in subsequent calls to the viFindNext operation to retrieve descriptor strings for the remaining instruments that were found.
This operation applies to VISA resource manager sessions only.
/*-------------------- Prototype ---------------------*/ViStatus viFindRsrc (ViSession Rsrc_Manager_Handle,   ViString Expression,   ViPFindList Find_Handle,   ViPUInt32 Return_Count,   char Instrument_Descriptor[]);
You can then set up code to wait until the resource you are looking for is ready and then open a session to it. Let me know if this helps out and have a great day!
Best Regards,
Adam G
National Instruments
Applications Engineer

Figuring out how to access a device using Windows.Devices.HumanInterfaceDevice?

Before I start, I would like to share this link I used to access windows RT libraries from Desktop applications (only the ones stated in MSDN documentation that are accessible from desktop applications):
http://blogs.msdn.com/b/cdndevs/archive/2013/10/02/using-windows-8-winrt-apis-in-net-desktop-applications.aspx .
After following the above instructions you can import some of the windows RT libraries in references. I have been trying to use the Windows.Devices.HumanInterfaceDevice library. I think my UsagePage and UsageId are off though. I am wondering
if someone good in hex can translate them from my report descriptor. I already have the VID and PID (this should be enough along with the path if I called write file or some of the other win32/OS api's). Here's the code I am using in VB.NET:
Public Class VirtualMouseDeviceOpen
Class Enumeration
' Enumerate HID devices
Public Async Function EnumerateHidDevices() As Task
Dim vendorId As UInt32 = &HBEEF
Dim productId As UInt32 = &HFEED
Dim usagePage As UInt32 = &HFF
Dim usageId As UInt32 = &H1
' Create a selector that gets a HID device using VID/PID and a
' VendorDefined usage
Dim selector As String = HidDevice.GetDeviceSelector(usagePage, usageId, vendorId, productId)
' Enumerate devices using the selector
Dim devices As Windows.Foundation.IAsyncOperation(Of Windows.Devices.Enumeration.DeviceInformationCollection) = DeviceInformation.FindAllAsync(selector)
Dim count As Integer = devices.GetResults.Count
If count > 0 Then
' Open the target HID device
' At this point the device is available to communicate with
' So we can send/receive HID reports from it or
' query it for control descriptions
Dim device As HidDevice = HidDevice.FromIdAsync(devices.GetResults.ElementAt(0).Id, FileAccessMode.ReadWrite)
Await Vendor.ReadWriteToHidDevice(device)
Else
' There were no HID devices that met the selector criteria
MsgBox("MUTT HID device not found!", MsgBoxStyle.Exclamation)
End If
End Function
Class Vendor
Public Shared Async Function ReadWriteToHidDevice(device As HidDevice) As Task
If device IsNot Nothing Then
' construct a HID output report to send to the device
Dim outReport As HidOutputReport = device.CreateOutputReport()
' Initialize the data buffer and fill it in
Dim buffer As Byte() = New Byte() {10, 20, 30, 40}
Dim dataWriter As New DataWriter()
dataWriter.WriteBytes(buffer)
outReport.Data = dataWriter.DetachBuffer()
' Send the output report asynchronously
Dim a As Windows.Foundation.IAsyncOperation(Of UInteger) = device.SendOutputReportAsync(outReport)
' Sent output report successfully
' Now lets try read an input report
Dim inReport As HidInputReport = device.GetInputReportAsync()
If inReport IsNot Nothing Then
Dim id As UInt16 = inReport.Id
Dim bytes = New Byte(3) {}
Dim dataReader__1 As DataReader = DataReader.FromBuffer(inReport.Data)
dataReader__1.ReadBytes(bytes)
Else
MsgBox("Invalid input report received")
End If
Else
MsgBox("device is NULL")
End If
End Function
End Class
End Class
Here's my report descriptor to avoid scrimmaging through everything trying to find it:
HID_REPORT_DESCRIPTOR G_DefaultReportDescriptor[] = {
0x06,0x00, 0xFF, // USAGE_PAGE (Vender Defined Usage Page)
0x09,0x01, // USAGE (Vendor Usage 0x01)
0xA1,0x01, // COLLECTION (Application)
0x85,CONTROL_FEATURE_REPORT_ID, // REPORT_ID (1)
0x09,0x01, // USAGE (Vendor Usage 0x01)
0x15,0x00, // LOGICAL_MINIMUM(0)
0x26,0xff, 0x00, // LOGICAL_MAXIMUM(255)
0x75,0x08, // REPORT_SIZE (0x08)
//0x95,FEATURE_REPORT_SIZE_CB, // REPORT_COUNT
0x96,(FEATURE_REPORT_SIZE_CB & 0xff), (FEATURE_REPORT_SIZE_CB >> 8), // REPORT_COUNT
0xB1,0x00, // FEATURE (Data,Ary,Abs)
0x09,0x01, // USAGE (Vendor Usage 0x01)
0x75,0x08, // REPORT_SIZE (0x08)
//0x95,INPUT_REPORT_SIZE_CB, // REPORT_COUNT
0x96,(INPUT_REPORT_SIZE_CB & 0xff), (INPUT_REPORT_SIZE_CB >> 8), // REPORT_COUNT
0x81,0x00, // INPUT (Data,Ary,Abs)
0x09,0x01, // USAGE (Vendor Usage 0x01)
0x75,0x08, // REPORT_SIZE (0x08)
//0x95,OUTPUT_REPORT_SIZE_CB, // REPORT_COUNT
0x96,(OUTPUT_REPORT_SIZE_CB & 0xff), (OUTPUT_REPORT_SIZE_CB >> 8), // REPORT_COUNT
0x91,0x00, // OUTPUT (Data,Ary,Abs)
0xC0, // END_COLLECTION
0x05, 0x01, // USAGE_PAGE (Generic Desktop)
0x09, 0x02, // USAGE (Mouse)
0xa1, 0x01, // COLLECTION (Application)
0x85, 0x02, // REPORT_ID (2)
0x09, 0x01, // USAGE (Pointer)
0xa1, 0x00, // COLLECTION (Physical)
0x05, 0x09, // USAGE_PAGE (Button)
0x19, 0x01, // USAGE_MINIMUM (Button 1)
0x29, 0x03, // USAGE_MAXIMUM (Button 3)
0x15, 0x00, // LOGICAL_MINIMUM (0)
0x25, 0x01, // LOGICAL_MAXIMUM (1)
0x95, 0x03, // REPORT_COUNT (3)
0x75, 0x01, // REPORT_SIZE (1)
0x81, 0x02, // INPUT (Data,Var,Abs)
0x95, 0x01, // REPORT_COUNT (1)
0x75, 0x05, // REPORT_SIZE (5)
0x81, 0x03, // INPUT (Cnst,Var,Abs)
0x05, 0x01, // USAGE_PAGE (Generic Desktop)
0x09, 0x30, // USAGE (X)
0x09, 0x31, // USAGE (Y)
0x15, 0x81, // LOGICAL_MINIMUM (-127)
0x25, 0x7f, // LOGICAL_MAXIMUM (127)
0x75, 0x08, // REPORT_SIZE (8)
0x95, 0x02, // REPORT_COUNT (2)
0x81, 0x06, // INPUT (Data,Var,Rel)
0xc0, // END_COLLECTION
0xc0 // END_COLLECTION
My UsageId is the first Usage Hex value in the report descriptor I believe (I am still a little confused too). My UsagePage is the hex values in the first Usage_Page in the report descriptor.
Note: the problem with the VB.NET code is that it returns 0 on the count above which means it did not find a device using my criteria.
Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - Sherlock Holmes. speak softly and carry a big stick - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog -
http://www.computerprofessions.us

Before I start, I would like to share this link I used to access windows RT libraries from Desktop applications (only the ones stated in MSDN documentation that are accessible from desktop applications):
http://blogs.msdn.com/b/cdndevs/archive/2013/10/02/using-windows-8-winrt-apis-in-net-desktop-applications.aspx .
After following the above instructions you can import some of the windows RT libraries in references. I have been trying to use the Windows.Devices.HumanInterfaceDevice library. I think my UsagePage and UsageId are off though. I am wondering
if someone good in hex can translate them from my report descriptor. I already have the VID and PID (this should be enough along with the path if I called write file or some of the other win32/OS api's). Here's the code I am using in VB.NET:
Public Class VirtualMouseDeviceOpen
Class Enumeration
' Enumerate HID devices
Public Async Function EnumerateHidDevices() As Task
Dim vendorId As UInt32 = &HBEEF
Dim productId As UInt32 = &HFEED
Dim usagePage As UInt32 = &HFF
Dim usageId As UInt32 = &H1
' Create a selector that gets a HID device using VID/PID and a
' VendorDefined usage
Dim selector As String = HidDevice.GetDeviceSelector(usagePage, usageId, vendorId, productId)
' Enumerate devices using the selector
Dim devices As Windows.Foundation.IAsyncOperation(Of Windows.Devices.Enumeration.DeviceInformationCollection) = DeviceInformation.FindAllAsync(selector)
Dim count As Integer = devices.GetResults.Count
If count > 0 Then
' Open the target HID device
' At this point the device is available to communicate with
' So we can send/receive HID reports from it or
' query it for control descriptions
Dim device As HidDevice = HidDevice.FromIdAsync(devices.GetResults.ElementAt(0).Id, FileAccessMode.ReadWrite)
Await Vendor.ReadWriteToHidDevice(device)
Else
' There were no HID devices that met the selector criteria
MsgBox("MUTT HID device not found!", MsgBoxStyle.Exclamation)
End If
End Function
Class Vendor
Public Shared Async Function ReadWriteToHidDevice(device As HidDevice) As Task
If device IsNot Nothing Then
' construct a HID output report to send to the device
Dim outReport As HidOutputReport = device.CreateOutputReport()
' Initialize the data buffer and fill it in
Dim buffer As Byte() = New Byte() {10, 20, 30, 40}
Dim dataWriter As New DataWriter()
dataWriter.WriteBytes(buffer)
outReport.Data = dataWriter.DetachBuffer()
' Send the output report asynchronously
Dim a As Windows.Foundation.IAsyncOperation(Of UInteger) = device.SendOutputReportAsync(outReport)
' Sent output report successfully
' Now lets try read an input report
Dim inReport As HidInputReport = device.GetInputReportAsync()
If inReport IsNot Nothing Then
Dim id As UInt16 = inReport.Id
Dim bytes = New Byte(3) {}
Dim dataReader__1 As DataReader = DataReader.FromBuffer(inReport.Data)
dataReader__1.ReadBytes(bytes)
Else
MsgBox("Invalid input report received")
End If
Else
MsgBox("device is NULL")
End If
End Function
End Class
End Class
Here's my report descriptor to avoid scrimmaging through everything trying to find it:
HID_REPORT_DESCRIPTOR G_DefaultReportDescriptor[] = {
0x06,0x00, 0xFF, // USAGE_PAGE (Vender Defined Usage Page)
0x09,0x01, // USAGE (Vendor Usage 0x01)
0xA1,0x01, // COLLECTION (Application)
0x85,CONTROL_FEATURE_REPORT_ID, // REPORT_ID (1)
0x09,0x01, // USAGE (Vendor Usage 0x01)
0x15,0x00, // LOGICAL_MINIMUM(0)
0x26,0xff, 0x00, // LOGICAL_MAXIMUM(255)
0x75,0x08, // REPORT_SIZE (0x08)
//0x95,FEATURE_REPORT_SIZE_CB, // REPORT_COUNT
0x96,(FEATURE_REPORT_SIZE_CB & 0xff), (FEATURE_REPORT_SIZE_CB >> 8), // REPORT_COUNT
0xB1,0x00, // FEATURE (Data,Ary,Abs)
0x09,0x01, // USAGE (Vendor Usage 0x01)
0x75,0x08, // REPORT_SIZE (0x08)
//0x95,INPUT_REPORT_SIZE_CB, // REPORT_COUNT
0x96,(INPUT_REPORT_SIZE_CB & 0xff), (INPUT_REPORT_SIZE_CB >> 8), // REPORT_COUNT
0x81,0x00, // INPUT (Data,Ary,Abs)
0x09,0x01, // USAGE (Vendor Usage 0x01)
0x75,0x08, // REPORT_SIZE (0x08)
//0x95,OUTPUT_REPORT_SIZE_CB, // REPORT_COUNT
0x96,(OUTPUT_REPORT_SIZE_CB & 0xff), (OUTPUT_REPORT_SIZE_CB >> 8), // REPORT_COUNT
0x91,0x00, // OUTPUT (Data,Ary,Abs)
0xC0, // END_COLLECTION
0x05, 0x01, // USAGE_PAGE (Generic Desktop)
0x09, 0x02, // USAGE (Mouse)
0xa1, 0x01, // COLLECTION (Application)
0x85, 0x02, // REPORT_ID (2)
0x09, 0x01, // USAGE (Pointer)
0xa1, 0x00, // COLLECTION (Physical)
0x05, 0x09, // USAGE_PAGE (Button)
0x19, 0x01, // USAGE_MINIMUM (Button 1)
0x29, 0x03, // USAGE_MAXIMUM (Button 3)
0x15, 0x00, // LOGICAL_MINIMUM (0)
0x25, 0x01, // LOGICAL_MAXIMUM (1)
0x95, 0x03, // REPORT_COUNT (3)
0x75, 0x01, // REPORT_SIZE (1)
0x81, 0x02, // INPUT (Data,Var,Abs)
0x95, 0x01, // REPORT_COUNT (1)
0x75, 0x05, // REPORT_SIZE (5)
0x81, 0x03, // INPUT (Cnst,Var,Abs)
0x05, 0x01, // USAGE_PAGE (Generic Desktop)
0x09, 0x30, // USAGE (X)
0x09, 0x31, // USAGE (Y)
0x15, 0x81, // LOGICAL_MINIMUM (-127)
0x25, 0x7f, // LOGICAL_MAXIMUM (127)
0x75, 0x08, // REPORT_SIZE (8)
0x95, 0x02, // REPORT_COUNT (2)
0x81, 0x06, // INPUT (Data,Var,Rel)
0xc0, // END_COLLECTION
0xc0 // END_COLLECTION
My UsageId is the first Usage Hex value in the report descriptor I believe (I am still a little confused too). My UsagePage is the hex values in the first Usage_Page in the report descriptor.
Note: the problem with the VB.NET code is that it returns 0 on the count above which means it did not find a device using my criteria.
Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - Sherlock Holmes. speak softly and carry a big stick - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog -
http://www.computerprofessions.us
I forgot anyone wanting a picture of what the device hierarchy looks like in control panel here it is (HID compliant vendor device is the first one in the report descriptor above I want to access and then the mouse device):
Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - Sherlock Holmes. speak softly and carry a big stick - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering - Yoda. Blog -
http://www.computerprofessions.us

Error code 0x0000000A installing Windows 10 Tech Preview on VirtualBox

Hello
I am trying to install Windows 10 Technical Preview on VirtualBox but I am receiving a message with the error code
0x0000000A
Parameters
0xFFD00000
0x000000FF
0x0000000A
0x81D171D3
I am tring to install with the archive WindowsTechnicalPreview-x86-EN-US.iso on a VirtualBox Configuration for Windows 8.1. (32 bits)
The parameter for hardware acceleration VT-x/AMD-V is enabled.
I have created before other virtual machines with other operating systems without issues.
All those machines have been created with the last updated release of VirtualBox what is 4.3.16. and that is the same one that I am using this time.
Thanks in advance
Regards
German

Do you have hardware support for virtualization on windows 8.1? Ensure that your VT-x/AMD-V acceleration is enabled also enable this feature in the BIOS setting menu.
Follow the given steps:
Reboot your computer and access the BIOS section> Advanced -> CPU Configuration
Click to enable the "No-Execute Memory Protection" option.
Go to Exit section. Choose Save Changes and Exit
Restart your system.
Here is a relevant Discussion, hopefully it would prove helpful:
https://forums.virtualbox.org/viewtopic.php?f=6&t=63125

Windows 10 Tech Preview Will Not Run On Oracle VM - Newest Build 2015

Hello Everyone,
I've been quite pumped to install the new Tech Preview for W10 on my VB.
I DL'ed the new ISO and tried to boot it up but it game me this error:
Failed to open the optical disk file.
Could not get the storage format of the medium (VERR_NOT_SUPPORTED).
Result Code:
VBOX_E_IPRT_ERROR (0x80BB0005)
Component:
Medium
Interface:
IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Callee:
IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee RC:
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
The version I'm trying to run the machine off on is Windows 8.1 x64 / Other Windows x64.
I gave it 4096MB of RAM, with 256MB of VRAM allocated to it. 3D Acceleration is also enabled. I'm not too sure if this is an Oracle VM problem, or an ISO problem. Any suggestions?
Thanks,
ScythianUnborne

I am trying to install Windows 10 in Virtual Box on my HP Pavilion DV6 running Windows 7 Home Premium x64. I set up the Win10 virtual machine following these instructions: http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/how-to-install-windows-10-developers-preview-in/e98dd450-02d2-4519-b6a3-6743bedcf777
However, I am receiving the following error: 'VT-x/AMD-V hardware acceleration is not available on your system. Certain guests (e.g. OS/2 and QNX) require this feature and will fail to boot without it.' When I click continue, the VM provides the following
message: 'Your PC needs to restart. Please hold down the power button. Error Code: 0x0000000A Parameters: 0xFFD00000 0x000000FF 0x0000000A 0x8192F5E3'
After some further research, I found that I need to enable virtualization and hyperthreading. I downloaded Speccy and determined that my PC is capable of virtualization, and it was already enabled; however, hyperthreading is not supported. I have been hearing
good things about Windows 10, and I should really like to give it a test run. Is the error with Virtual Box or Windows 10 or Windows 10 running in Virtual Box? Is there anything I can do to make it work? Thanks for any help.
Any reason why you would not consider dual boot Win 7 and Win 10 TP ?
I had an Acer Aspire laptop running Win 7 Home Premium SP1 64-bit. I dual booted with Win 10 TP. That's starting from build 9841 to 9926. I dual booted twice and I had no problem doing it.

Is WindowsAPICodePack.Sensors Still valid for accessing sensors on Latest Windows Build ( Technical Preview Windows 10)

Hello,
I have been an avid user of Microsoft.WindowsAPICodePack.Sensors for accessing the sensors(HID,non HID) since WIndows 7 days.But recenlty I have found some exception coming while accessing the same code in the Windows 10 technical preview(build 1041
: from here -->
http://windows.microsoft.com/en-us/windows/preview-iso-update-1503).
I am using build 10041 and the below is the portion of the code giving me attached Exception Continously.The code works fine on Windows 7/8/8.1
using Microsoft.WindowsAPICodePack.Sensors;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
namespace TestWindowsAPICodePackSensors
    class Program
        static void Main(string[] args)
            SensorList<Sensor> sensors =     SensorManager.GetAllSensors();
            Console.WriteLine("There are " + sensors.Count +" sensor(s) installed on the system.");
Kindly assist , is this is the bug in the build or I have to use somethign else for Windows 10.
Thanks and Rgds,
S

Any update on this.
Thanks in advance !
Rgds,S

Windows 10 tech preview Help

I installed the new tech preview of windows on 2 different laptops.
1 has an NVidia video card and the other has an ATI card.
I installed 12.1.1.4 on both. on the NVidia machine there is no problem.
On the ATI system it worked until the video driver updated.
Hasn't worked since. Has anyone ever had a similar experience and found a workaround without rolling back the driver???
Can any one help???
Thanks in advance.

Hi Mike,
So the current situation is we are running Windows 10 9841 on the machine which used to run Windows XP, and the install process is very slow?
Have you checked the system requirements before the installation?
Before you install Windows Technical Preview
Could you please have a share with the machine specifications?
Besides, if you are willing to upgrade to the newer version (Build 9879, also Windows 10 9879 ISO is available for download), you might encounter the disk missing error. Build 9879 introduced functionality that used the
PUIS (Power-Up in Standby) function of hard disks. This causes the hard disk to not spin up when power is applied, it instead waits for a separate spin-up command.
Some system firmware does not send this command and thus the hard disks are either not seen in BIOS or appear incorrectly. This has been fixed by update
KB3021937.
For more details, please check this thread:
build 9879 bricking drives!!!!
Best regards
Michael Shao
TechNet Community Support

How to access USB HD on Windows?

I am able to connect to my usb hardrive on the mac's on my network, but I am unable to see the drive on the windows. What or how do I do access the drive?

Ok, let's double-check the file sharing setup on your AEBSn...
AirPort Extreme Base Station (AEBSn) - File Sharing Setup
Either connect to the AEBSn's wireless network or temporarily connect your computer directly (using an Ethernet cable) to one of the LAN ports of the AEBSn, and then, using the AirPort Utility in Manual Mode, check these settings:
Disks - File Sharing
- Secure Shared Disks: <With disk password | With base station password | With accounts >
(Note: Choose "With a disk password," or "With base station password" if you want to secure the shared disk with a password, or choose "With accounts" if you want to secure the disk using accounts.
If you choose to use accounts, click Configure Accounts, click the Add button, and then enter a name and password for each user that will access the disk.)
- Guest Access: <Not allowed | Read only | Read and write>
- Share disks over Ethernet WAN port: (unchecked)
(Note: Select the "Share disks over Ethernet WAN port" checkbox if you want to provide remote access to the disk over the WAN port.)
- Advertise disks globally using Bonjour: (unchecked)
- Workgroup: <Windows workgroup name>
- WINS server: <WINS server IP address>

No telnet server in Windows 10 tech preview

When I went to enable a telnet server in Windows 10 preview by going to "Turn Windows features on or off," I noticed that there is no option for Telnet Server like there is in Windows 8.1. Running tlntadmn on the command line produces nothing,
as does searching for it in on my drive. Is Telnet Server just not available for this OS yet?
KeepMyIdentities, Your Key to Password Security. Available now on the Windows Store: http://apps.microsoft.com/webpdp/en-US/app/keepmyidentities/61a9f340-97ac-4666-beab-39f9246cb6fa

I just want to mention that by removing Telnet server Microsoft has just broken, from our organization alone, close to a thousand automated tests for verifying our drivers
work with the OS. I am sure this is being repeated at hundreds of businesses around the world. Additionally, there are thousands of system administrators who have automated scripts using Telnet for managing their PCs.
Offering Remote Desktop as an alternative is beyond ridiculous. At the very least, Microsoft should offer SSH as an alternative. While
this requires a lot of rework, at least it is an option. Personally, I am tired of having to find, download, and install 3rd party software in order to do my job.

Accessing USB device in Windows 10 Tech Preview under Hyper-v

Similar Messages

Maybe you are looking for