the docking keyboard

Ronin · January 2, 2021, 4:16pm

H10 Q64G42171000769 tablet does not recognise it the docking keyboard , unknown USB device ( unsuccessful device descriptor request )

EndlessBiginner · January 3, 2021, 1:43am

Sorry, it doesn’t seem to be a keyboard hi10.
Looking at the picture, the distance between pin contacts is different and the width of body is different. How do you attach it to Hi10…

If you could, it’s good to send it back to the seller and request refund.

Ronin · January 4, 2021, 6:41pm

As the first is on a picture, allow onto the thorns.
The sending back may not be already, two I bought it eating the ebay.
It was not said till now, that not good.
Many drivers I downloaded it from CHUWI side, but one were out of order.

CHUWI gave advices like this:

pls try to reinstall the Intel HD grafics driver CHUWI SERVICE

If your keboard does not work, Please try the following 3 measures

First, restart your tablet.

Second, update firmware
setting–system–about tablet—wireless update

Third, please reinstall the OS

Thank you for the help ! (google translator)

Ronin · January 4, 2021, 6:43pm

at least two of his years Roger, I made an attempt a lot since then

EndlessBiginner · January 5, 2021, 1:23am

I think you’ve already tried this, let me introduce…

open command prompt (cmd.exe)
execute chkdsk /f /r /x
restart PC (this may take more than a few hours)

P.S. the keyboard you have may be suitable for HiPad X. Check this.

Ronin · January 5, 2021, 4:48pm

If I run the command, this message:
Access Denied as you do not have sufficient privileges or
the disk may be locked by another process.
You have to invoke this utility running in elevated mode
and make sure the disk is unlocked.

EndlessBiginner · January 5, 2021, 10:13pm

Hi.
I should explain that Administrator privilege is required to use chkdsk, sorry.

You can use PowerShell instead of cmd.exe.
In this case, Admin. privilege is also required, therefore,

Right-click the Windows Icon at the bottom-left of screen. Menu appears.

Untitled1461×963 33.8 KB
Clidk “Windows PowerShell (Admin)”. Then you will be asked “Do you want to allow this app. to make changes to your device ?”, click “Yes”
PowerShell runs with Administrator privilege. Execute chkdsk /f /r /x.

Untitled31348×1096 13.9 KB

P.S:
If the situation is not improved after the procedure above, try to run sfc /scannow
This may take 30min.~1 hour.

Ronin · January 6, 2021, 7:01pm

I ran it as a system administrator

chkdsk/f/r/x : The term ‘chkdsk/f/r/x’ is not recognized as the name of a cmdlet, function, script file, or operable pr
ogram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

chkdsk/f/r/x

  + CategoryInfo          : ObjectNotFound: (chkdsk/f/r/x:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

PS C:\WINDOWS\system32> sfc/scannow
sfc/scannow : The term ‘sfc/scannow’ is not recognized as the name of a cmdlet, function, script file, or operable prog
ram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

sfc/scannow

  + CategoryInfo          : ObjectNotFound: (sfc/scannow:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

EndlessBiginner · January 6, 2021, 10:12pm

Command includes SPACE characters. input command precisely.

chkdsk /f /r /x

(not “chkdsk/f/r/x”)

sfc /scannnow

(not “sfc/scannow”)

Ronin · January 7, 2021, 7:34pm

newer attempt

PS C:\WINDOWS\system32> chkdsk f r x
Invalid parameter - r
PS C:\WINDOWS\system32> chkdsk f x
Invalid parameter - x
PS C:\WINDOWS\system32> chkdsk f
The drive, the path, or the file name is not valid.
PS C:\WINDOWS\system32> chkdsk r
The drive, the path, or the file name is not valid.
PS C:\WINDOWS\system32> chkdsk x
The drive, the path, or the file name is not valid.
PS C:\WINDOWS\system32>

PS C:\WINDOWS\system32> sfc scannow

Scans the integrity of all protected system files and replaces incorrect versions with
correct Microsoft versions.

SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=] [/VERIFYFILE=]
[/OFFWINDIR= /OFFBOOTDIR= [/OFFLOGFILE=]]

/SCANNOW Scans integrity of all protected system files and repairs files with
problems when possible.
/VERIFYONLY Scans integrity of all protected system files. No repair operation is
performed.
/SCANFILE Scans integrity of the referenced file, repairs file if problems are
identified. Specify full path
/VERIFYFILE Verifies the integrity of the file with full path . No repair
operation is performed.
/OFFBOOTDIR For offline repair, specify the location of the offline boot directory
/OFFWINDIR For offline repair, specify the location of the offline windows directory
/OFFLOGFILE For offline repair, optionally enable logging by specifying a log file path

e.g.

Ronin · January 7, 2021, 7:36pm

chkdsk f r x there was white space

Ronin · January 7, 2021, 7:37pm

there was space chkdsk f r x

EndlessBiginner · January 7, 2021, 8:59pm

I think you can run chkdsk properly because of this message from your reply.

This response is not shown except chkdsk is executed correctly.
Otherwise, you need to ask someone nearby you to manipulate PC.
Or try to cut & paste command lines from my reply.

PS.
The reason why I recommend you to use chkdsk and sfc is that your PC settings seem to be corrupted. Regardless a keyboard is connected or not, USB descriptor should be recognized. At first, we need to confirm that Windows settings are normal.

Ronin · January 10, 2021, 6:20pm

I settled it on new one the windowst,i ran the command.
What may I do yet?

PS C:\WINDOWS\system32> chkdsk f
The drive, the path, or the file name is not valid.
PS C:\WINDOWS\system32> chkdsk r
The drive, the path, or the file name is not valid.
PS C:\WINDOWS\system32> chkdsk x
The drive, the path, or the file name is not valid.
PS C:\WINDOWS\system32> sfc scannov

Scans the integrity of all protected system files and replaces incorrect versions with
correct Microsoft versions.

SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=] [/VERIFYFILE=]
[/OFFWINDIR= /OFFBOOTDIR= [/OFFLOGFILE=]]

/SCANNOW Scans integrity of all protected system files and repairs files with
problems when possible.
/VERIFYONLY Scans integrity of all protected system files. No repair operation is
performed.
/SCANFILE Scans integrity of the referenced file, repairs file if problems are
identified. Specify full path
/VERIFYFILE Verifies the integrity of the file with full path . No repair
operation is performed.
/OFFBOOTDIR For offline repair, specify the location of the offline boot directory
/OFFWINDIR For offline repair, specify the location of the offline windows directory
/OFFLOGFILE For offline repair, optionally enable logging by specifying a log file path

e.g.

    sfc /SCANNOW
    sfc /VERIFYFILE=c:\windows\system32\kernel32.dll
    sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows
    sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows /OFFLOGFILE=c:\log.txt
    sfc /VERIFYONLY

PS C:\WINDOWS\system32>

EndlessBiginner · January 10, 2021, 8:38pm

you must ask some one to input command precisely instead of you
because you seem to be unable to input “/”.

Sincerely

Ronin · January 24, 2021, 3:13pm

chkdsk c: /f /r /x 100%

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\WINDOWS\system32> sfc /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
PS C:\WINDOWS\system32>

PS C:\WINDOWS\system32> sfc /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

VID/PID VID is not for the device/the identifier of your pi

EndlessBiginner · January 25, 2021, 1:33am

Thank you for a lot of efforts.
Your native language seems to be Hungarian. (mine is Japanese)
It’s a hard work to communicate using second language.
Some minor errors seemed to be found and solved.

Two situations can be guessed

the keyboard responds to PC with invalid VID (vendor ID)
the keyboard is not suitable for PC

I think it’s best to exchange the keyboard with another keyboard for Hi10. Could you contact the seller where you bought the keyboard?

Ronin · January 26, 2021, 4:00pm

2018 I was shopping, the Ebay does not remember already, that from who.
I say thank you for the help very much.

Topic		Replies	Views
ChuWi Hi10 Model CWI515 - docking a Keyboard Ask A Question	16	388	March 17, 2024
I need help please Hi10 Air	0	502	November 17, 2020
Hipad LTE Docking Keyboard HiPad/HiPad LTE	4	1078	April 23, 2020
Keyboard fail :frowning: Hi10 X	7	1935	April 4, 2022
HiPad Plus does not recoginize Bluetooth keyboard with Touchpad HiPad Plus	1	636	March 21, 2022

the docking keyboard

Related topics