First character is lost when I search for something quickly with Cortana

If I choose "Replace Start 10 search with Cortana" and then whenever I press Start and start typing, my first character always get lost. i.e. if I type "bluestacks", cortana will search for "luestacks".

 

I am facing this issue from last several years, but nobody care about fixing it

24,626 views 39 replies
Reply #1 Top

Hello,

Sorry to hear you are having issues. On my system it works with first keystroke. Just sometimes it happened that the first keystroke is somehow used/lost to wake the Cortana, and every time after that the first keystroke get registered for search. If on your system the first keystroke is lost everytime. Please try purge and reinstall : https://forums.stardock.com/486022/start10-support-faq#reinstalling

Reboot, retest and report back. Thanks

Basj,

Stardock Community Assistant.

Reply #2 Top

> first keystroke is somehow used/lost to wake the Cortana

 

Maybe that's the issue. How do I fix it? I think it happens if I use search after a while.

 

I am having this issue since several years. I am able to reproduce it in 3 different laptops I have tried at.

Reply #3 Top

I think that is more on how Windows 10/Cortana Work. But may I suggest to use the Windows 10 Start Menu instead the Start10 menu when you need to search for something. i.e pressing the right windows key on the keyboard or if you don't have it you can turn on the options below.

Thank you,

 

Basj,

Stardock Community Assistant

Reply #4 Top

It's not a good solution. Start10 should wake up cortana before sending user input. I am also a developer, so I know it's possible to do it.

We can look for workarounds, or we can fix the actual bug.

Reply #5 Top

Hello,

I have forwarded your problem to Stardock Support team for their assistant. Please keep an eye on this thread for any updates. We appreciate your feedback and patient.

Basj

Stardock Community Assistant.

Reply #6 Top

If I choose "Replace Start 10 search with Cortana" and then whenever I press Start and start typing, my first character always get lost. i.e. if I type "bluestacks", cortana will search for "luestacks".
End of quote

We cannot reproduce your issue.

How are you 'pressing Start'? Touchscreen, Windows Key, mouse, Ctrl + Esc?  If one is often used by you, do the other ways not have that issue?

Perhaps a purge and reinstall is in order:

https://forums.stardock.com/486022/start10-support-faq#reinstalling

Reply #7 Top

@basj confirmed he can reproduce the issue.

Reply #8 Top

Hello.  I can also report the same issue, including in the current beta.

 

The explanation that the first keypress is "waking up Cortana" doesn't seem right, because my experience is that the first letter appears as the SECOND letter when I type quickly.

For instance, if I click start and then type      netsh

...what appears in the search box is               entsh

It is never "eating" the first letter in my experience, it is delaying the first letter and inserting it late -- so it becomes the second letter.  I can readily reproduce this behavior.

Very frustrating for a fast typist.

 

Thanks in advance for a genuine solution.  Perhaps Start10 needs to collect more letters and then forward them to Cortana in the proper order.

Reply #9 Top

Hello,

I no longer be able to reproduce the issue on my system. Maybe something change, but not really sure what.

Need more information on your system.

1) Windows 10 version. Please use Winver.exe for full version numbers.

2) Start10 version.

3) Please upload a video of this issue to a video sharing site and post the link here.

Thank you,

Basj
Stardock Community Assistant.

Reply #10 Top

Hi.  Windows 10 v2004 (OS Build 19613.1000)

Start10 v1.93

Video at http://youtu.be/7NfftAsBlyQ?hd=1

 

In the video, I am typing           netsh              very quickly - yes -- but definitely hitting the n before the e.

Reply #11 Top

Hello,

Its look like you are running Windows 10 insider preview version which is not supported. But, I have forwarded your questions/problems to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #12 Top

Oh please.  With all due respect, don't give me the "unsupported version" stuff.

Today's insider version is tomorrow's release version -- you need to know what's coming and deal with it.

I opened a support ticket, and was asked to move my concern to the forum.  So I do that, take the trouble, and then you give me "unsupported...".

Not helpful.  Your years-long customer, jim

Reply #13 Top

Hello,

I never said your issue will be ignored. I did mentioned that the issue was pushed to Support for them to review it. As for "Windows 10 insider preview release" not supported. It is the decision informed to us from above. And I believe the decision made is reasonable, since, we have seen so many times Microsoft "Official" released updates with issues.

Thank you,

Basj
Stardock Community Assistant.

Reply #14 Top

I still face this issue in stable version too.

 

I have even tried waking cortana every minute using "plmdebug.exe" utility. Still had same problem.

Reply #15 Top

Hello,

Sorry to hear you are having trouble.

I have logged your report and it is being reviewed internally.

Internal ref: ODNT-590

Thank you for the reports.

Sean Drohan
Stardock Support Manager

Reply #16 Top

Wow it's good to see I'm not the only one with this issue. I thought I was going crazy and swapping letters.  Windows 10, 1909, latest version of Start10 as of this moment.

Reply #17 Top

if I was you, I won't get excited. This issue is open for 2 years and Stardock is still not interested in fixing it.

Reply #18 Top

Quoting tesasasast5, reply 17

if I was you, I won't get excited. This issue is open for 2 years and Stardock is still not interested in fixing it.
End of tesasasast5's quote

Please see:

https://forums.stardock.com/489754/get;3776939

Sean Drohan
Stardock Support Manager

Reply #19 Top

Sean, the link you posted just takes us back to this same thread.

Reply #20 Top

Quoting jaddorf, reply 19

Sean, the link you posted just takes us back to this same thread.
End of jaddorf's quote

Yes, it does...;)

 

Reply #21 Top

+1

Happens on all windows 10 devices I have tried it with. (2 desktops and 3 laptops)

 

Reply #22 Top

Just wanted to report that I, too, am getting the same behavior with the first 2 characters swapped. 

Windows Version 1909 (OS Build 18363.836)

Start10 Version 1.94

Reply #23 Top

Add me to the list with the same issue, the first 2 characters often get swapped when typing in search quickly after pressing windows key. Quite frustrating!

This doesn't happen in regular windows start menu..

Windows Version 2004 (OS Build 19041.329)

Start10 Version 1.94

Reply #24 Top

This issue affects me on three different computers, all running Start10 1.94.

Computer 1: Dell Latitude 7410 running Windows 10 Pro 1909 Build 18363.959
Computer 2: Dell Precision 3630 running Windows 10 Pro 1909 Build 18363.959 (accessed via remote desktop)

  • First character is dropped completely from search input

Computer 3: Self-built AMD 3700X + X570 desktop running Windows 10 Pro 2004 Build 19041.388

  • First two characters are often swapped

The character dropping issue generally only occurs after a fresh reboot (on Computer 2, via remote desktop, it is reproducible more often). The character swap issue is easy to reproduce as often as I like. For both, I generally always click the start menu with my mouse rather than using a keyboard shortcut.

Reply #25 Top

I believe Sean already mentioned that this issue was acknowledged and logged internally in May. And I strongly believe that the Dev team is working on it now. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant