PD12.2 + Windows 10 creators update = Keyboard not working, explorer freezing, task scheduler crash.

Discussion in 'Windows Guest OS Discussion' started by DawidM, Apr 25, 2017.

  1. EmilW

    EmilW Bit Poster

    Messages:
    2
    @Dmitry@Parallels Can we get Parallels take on the fix/hack suggested by @MikeS14? It seems to be working better than anything coming from your end.
     
  2. LinF

    LinF Bit Poster

    Messages:
    1
    MikeS14's solution fixed my problem completely. Like the others, this problem started very mysteriously recently. I was not even running the Creators Update, nor the Anniversary Update, I was still running on the 1511 update, I did have Office and Outlook. The symptoms on 1511 were strange failures and error messages during login, sometimes the handle is invalid, sometimes SessionEnv failed, or sometimes systemprofile\desktop unavailable, or just stuck on the Welcome message. When it did login, sometimes starting a program for the first time would give the stub is bad message. I was able to install the Creators Update hoping it would correct the problem, it did not, the symptoms continued, plus the ctfmon.exe problem that started happening and Google led me here. Seems like Parallels is a common thread in this problem.
     
  3. FransH1

    FransH1 Bit Poster

    Messages:
    2
    Updated to Parallels Desktop Version 13.0.1 (42947)
    Still have the same problems. Will try MikeS14's solution now.
    >> after the change in the register Windows works normal again, the taskbar responds immediately and the keyboard responses.
    >>>> Parallels, use this to fix this!
     
    Last edited: Sep 4, 2017
  4. BurkhardP

    BurkhardP Bit Poster

    Messages:
    9
    The trouble with the task bar not responding, restarting and not reacting on keystrokes started three days ago with my Windows 10 VM running on Parallels 11.
    I updated to PD 13 but the trouble still remained. Spent des whole day today with this annoying thing.

    But MikeS14's solution solved the problem! Just changed the registry value from 3 to 0 and rebootet as described in post #36.
    Great job! Thank you!
     
  5. KevinZ2

    KevinZ2 Bit Poster

    Messages:
    1
    I'm not using windows 10 much and only just discovered the same problems here this week. MikeS14's solution seems to have worked.

    Seems to be many posts going on about this. It would be nice for Parallels to fix this once and for all.

    Thanks
     
  6. MarkT9

    MarkT9 Bit Poster

    Messages:
    2
    SOLVED! (At least for the moment.)
    This issue has been plaguing my Windows for months! I'd become resigned to the fact that it takes 10+ minutes just to sign into Windows and that I can't use the start menu and that the keyboard doesn't work in most apps. (Yes, that basically means Windows is completely unusable.)

    And just for the record, I'm a computer engineer with a specialty in operating systems. So I've worked pretty hard to try to troubleshoot, understand, and solve this problem. And every month or two, I'll try to see if I can search for someone who has any ideas on a solution, but always end up frustrated....until now!

    I applied MikeS14's recommended registry key change (see earlier post), rebooted, and Windows came up immediately, let me log in immediately, and the start menu and keyboard worked immediately. Windows is usable again!

    To the Parallels team: the thread on this topic on the Microsoft community site suggests that you may be actively modifying the registry key in question. If that's the case, please, please, please have your dev team look at how they might address this. Parallels is awesome and is definitely worth the price...when it works. But I bought it solely to run Windows, so when Windows is practically unusable, I (and many others) have no reason to continue to give you money.

    Thank you MikeS14!! And thanks in advance for a permanent solution, Parallels team!

    [ If it helps others: I'm running Windows 10 Home (version 1607 14393.1480) as a VM under Parallels 12 (12.2.1 - 41615) on a Mac (El Capitan 10.11.6). ]
     

Share This Page