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

Dmitry@Parallels said:
Guys, @ForrestC1, we have released a hotfix for Parallels Desktop 12 version 12.2.1 (41615) where we've fixed an issue with VisualStudio (https://forum.parallels.com/threads...arallels-12-upon-awakening-from-sleep.339941/) and several more.

Please let me know if this hotfix changes the VM behavior for anyone.
If not, then we need you to try the following:

1. This behavior might be related to Windows hiberboot (aka hybrid shutdown). Please disable this feature via command prompt using this command, then restart and check the results:

powercfg -H off

2. Try to re-create user profile following these steps: https://neosmart.net/wiki/corrupt-user-profile/#Fix_1_Registry_Editor. Check if ctfmon.exe now starts correctly.

Will be looking forward to your results.
Click to expand...

Hello Dmitry,

I do have the same issue as described.
My Parallels version : 12.2.1 (41615)
The problem persists and the 2 solutions you suggest are not resolving the issue
.
The startup of Windows is taking a long time (sometimes it stops with a message "The Handle is Invalid".
Once up I need to do the ctfmon.exe workaround.

Best Regards,

Andre
 
Well, this is very frustrating issue and the creators update has lots of issues with it. There are many issues and errors users are facing after updating their windows 10 operating system.
However to fix the Creators Update keyboard issues update the drivers related to the keyboard. Or else check for the Microsoft site whether any latest update is rolled out to fix the Creators updates related issues. For installing creators update check the minimum requirements of the PC and especially the space required for installing the update in the drive.

For other Windows issues visit: https://sites.google.com/site/troubleshootwindows10problems
 
lorein said:
Well, this is very frustrating issue and the creators update has lots of issues with it. There are many issues and errors users are facing after updating their windows 10 operating system.
However to fix the Creators Update keyboard issues update the drivers related to the keyboard. Or else check for the Microsoft site whether any latest update is rolled out to fix the Creators updates related issues. For installing creators update check the minimum requirements of the PC and especially the space required for installing the update in the drive.

For other Windows issues visit: https://sites.google.com/site/troubleshootwindows10problems
Click to expand...
Hello Lorein,

I did NOT install the windows creators update.
This happened after upgrading parallels to 12.2.1 without doing any windows update.
So in my humble opinion this is a parallels issue and I suggest parallels to take this seriously and not fingerprint to windows.
I am daily loosing valuable time.

BR,

Andre.
 
Same issues (slow start, no keyboard) on Windows 10 Pro + all updates installed with PD Pro 12.2.1 (41615) on OS X 10.12.5
What can i do ? What can you suggested ?
 
Last edited:
I also had the same problem.
It initialized from Windows 10 setting and solved it.

[Windows 10 Setting]
"Update & Security" -> "Recovery" -> "Reset this PC"
(Choose Delete Application as well)

Reinstall Parallels Tools after Restore
 
Hi Community,
I have the same Problem here.
The Scedular is not runnig. After a lot of minutes the system keep calm. (see the video before, same here)
I run the ctfmon.exe and I can use the Keyboard again.

A month ago I had the same problem already. I reinstall the whole system, and it work.
But now, after a further update, same Problem.
That is not funny. I won't reinstall the system after each update by Microsoft....

Is there a solution (update by Parallels etc..)?
And an important Detail. I cant restart the system after a new security update is comming by MS. Because the scheduler service is not running.

upload_2017-7-19_9-51-18.png

upload_2017-7-19_10-6-3.png
 
Last edited:
Same here on Win 10 Pro 64bit 1607, Parallels Desktop 12 version 12.2.1 (41615) did nothing to alleviate issue. This is ONLY happening AFTER Parallel Tools is installed, it has something to do with Parallel Tools, tell the devs to fix it already, how long are they going to let this go, this is disgraceful.
 
Echoing the same problem. ctfmon only fixes keyboard, not task scheduler (or software protection) failure (UBPM.dll fault). Restarting explorer and removing Parallel Tools does not seem to have any impact.
Windows update (2017-08 Cumulative Update) was possible by running the Troubleshooter and fixing a database error. Did not fix the problems.
UBPM.dll fault is likely behind everything. AppCrash logs show:
Version=1
EventType=APPCRASH
EventTime=131471892414105369
ReportType=2
Consent=1
ReportStatus=4096
ReportIdentifier=19d12781-e00f-4e21-957a-17d90940c667
IntegratorReportIdentifier=30a551bb-87ca-4677-8c9b-0906022899c4
Wow64Host=34404
NsAppName=svchost.exe_Schedule
AppSessionGuid=0000167c-0000-0022-5092-a354fd14d301
TargetAppId=W:0000f519feec486de87ed73cb92d3cac802400000000!0000fd9154ec5fed8b2ee3a71e95cf62601ac9296509!svchost.exe
TargetAppVer=1971//04//26:14:43:01!15d07!svchost.exe
BootId=4294967295
ServiceGroupName=netsvcs
ServiceDllName=schedsvc.dll
ServiceSplit=1
TargetAsId=116
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=svchost.exe_Schedule
Sig[1].Name=Application Version
Sig[1].Value=10.0.15063.0
Sig[2].Name=Application Timestamp
Sig[2].Value=02799ef5
Sig[3].Name=Fault Module Name
Sig[3].Value=UBPM.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.15063.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=3c1e9962
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000002cf48
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.15063.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=4105
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=85cf
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=85cf59fe571008edaac2164289cee481
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=8136
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=81364e25c1a8725bf64414bf521ad02f
UI[2]=C:\WINDOWS\system32\svchost.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=Task Scheduler stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\WINDOWS\system32\svchost.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\sechost.dll
LoadedModule[5]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[6]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[7]=C:\WINDOWS\System32\combase.dll
LoadedModule[8]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[9]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[10]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[11]=C:\WINDOWS\System32\user32.dll
LoadedModule[12]=C:\WINDOWS\System32\win32u.dll
LoadedModule[13]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[14]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[15]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[16]=c:\windows\system32\schedsvc.dll
LoadedModule[17]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[18]=c:\windows\system32\UBPM.dll
LoadedModule[19]=c:\windows\system32\EventAggregation.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\WLDP.DLL
LoadedModule[21]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[22]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[23]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[24]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[25]=c:\windows\system32\AUTHZ.dll
LoadedModule[26]=C:\WINDOWS\System32\POWRPROF.dll
LoadedModule[27]=c:\windows\system32\WMICLNT.dll
LoadedModule[28]=C:\WINDOWS\system32\sspicli.dll
LoadedModule[29]=c:\windows\system32\bcrypt.dll
LoadedModule[30]=C:\WINDOWS\system32\taskcomp.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\cryptsp.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\ntmarta.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Task Scheduler
AppPath=C:\WINDOWS\system32\svchost.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=E60FA585B8DB2F82FBA30172963FACDA
MetadataHash=-1511101469

Update: I did find one reference in a Windows forum that this might be related to a C++ Redistributable library, and I noted that my Visual C++ 2012 Redistributable was listed in the Apps as being installed in July 2017. Removing it had no effect. This problem is all over the Windows forums and may be completely unrelated to Parallels.
I have also tried removing my second monitor, operating in Windowed, full screen and Coherence mode.
 
Last edited:
Same problem here. This is a freaking disaster, can't believe Parallels has yet to fix this. Can't type into any modern apps unless I force ctfmon to run. Scheduler is broken. Desktop keeps crashing and restarting (task bar flashes). Language bar disappears. Sometimes I can't even get a list of users for login when I send the VM a CTL-ALT-DEL. Login is sometimes fast, sometimes ridiculously slow. Shutdown sometimes generates a black screen of death. I have to stop and re-start Parallels Desktop between VM sessions or it doesn't work right. This is such a mess. I wasted bunches of hours trying to isolate the problem before finding this thread. I sent in a report, can't remember the number, but it's not like you haven't seen this 500 times by now. Where are your devs, why aren't you fixing this? This is, quite frankly, an existential threat to Parallels. Until I can usefully run Windows on Parallels, I have wasted my money and you have no reason to exist. You might want to get this fixed.

Parallels Desktop 12 for Mac: Version 12.2.1 (41615), Windows 10 Version 1703 (Build 15063.540)
 
Last edited:
I have the same problem here. All of a sudden the task scheduler service fails to start, causing issues in modern apps and start menu. I can start ctfmon.exe to fix the keyboard problem, but with task scheduler not running I know this will be causing other issues...

Has someone found a solution beside doing a clean install?
 
SOLVED -- with caveat; I do not know the full impact of making this change.
In my case, I run regular scheduled tasks, and I can track the Task Scheduler operation up to a point at which an Office update kicked in (which changed Microsoft.Office.Tools.Outlook.v9.0.ni.dll and ???). After that, the task scheduler no longer logged to the system event logs. The last entry was changing maintenance state to 3. It appears the task scheduler was put into maintenance mode and left in that state. That causes the task scheduler to fail which causes all kinds of background services to stop working.

WHAT I DID:
1 is this your problem? Control panel> System and Security > Security and Maintenance > expand Maintenance section > Automatic maintenance shows "maintenance in progress" and you can't "Stop maintenance".
2. hack: use regedit to change maintenance state to 0 (I HAVE NO IDEA WHAT THIS COULD DO OR IF THIS IS THE "RIGHT" VALUE):
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\Maintenance\State > ReportedState changed from 3 to 0

Reboot VM...and everything seems to be back in normal operational state. WOULD LOVE IT is someone 'in the know' could tell me if this was a bad thing to do :))

Good luck!

UPDATE: 2017-08-21 This fix does not solve everything. I have noticed, among other things, that the date/time does not automatically update when coming out of suspend. Be wary of odd behaviour...
UPDATE: 2017-09-05 Turns out I forgot to UNDO the changes to create a clean boot, so all the third party services were not starting up. Fixed that and everything seems to be back to normal now.
 
Last edited:
The solution posted by MikeS14 worked for me. I recently installed Office so it could explain why I wasn't affected by the problem until now. I don't know if PD12 has anything to do with it or not, but it seems like an interesting coincidence why the first link on Google matching my problem was on this forum. Thanks a lot everyone!
 
Hi together,

thanks to Mike24, it seems the Scheduler is running again, hopefully to the full extent.
But not the Keyboard. I still have executed the ctfmon.exe
But that is the smallest issue, but it is a unsatisfactorily fact.

This case is not complete solved

Greeds Falk
 
I think it is something in between.
But I use both iMAC and a windows PC. On windows PC I never had this Problems.
So I think it's something, who can tell us the Parallel guy's, but I can't see no response by them here???

Greeds
Falk
 
You must log in or register to reply here.
Back
Top