Can't launch 64-bit OSK.EXE from 32-bit Total Commander

[ib]

I'm trying to launch 64-bit C:\Windows\System32\osk.exe from 32-bit Total Commander, but getting the error message "Could not start On-Screen Keyboard". I can launch the file from Windows Explorer, but get the same error message if I try to launch the 32-bit C:\Windows\SysWOW64\osk.exe (both from TC and Explorer).

Any ideas?

My system:
Windows 10 Enterprise 64 bit Version 1607 (OS Build 14393.693)
Total Commander Version 9.0a 32 bit (2016-12-14)

I have searched the forum for a similar issue but failed finding it.

[Dalai]

Take a closer look at the Windows\system32 directory and you'll see that it doesn't contain what you think it contains. More on this topic can be found e.g. in this pinned thread.

Regards
Dalai

[tuska]

For me it looks like this...

Code: Select all

!----------------------!---------!------------------!-------------------------------------------!
! Path                 ! osk.exe ! TC + Explorer    ! Windows                                   !
!----------------------!---------!------------------!-------------------------------------------!
! C:\Windows\System32  !   NOK   ! 9.0a 32bit       ! 10 Pro x64 Version 1607 (Build 14393.693) !
! C:\Windows\SysWOW64  !   NOK   ! 9.0a 32bit       ! 10 Pro x64 Version 1607 (Build 14393.693) !
!----------------------!---------!------------------!-------------------------------------------!
! C:\Windows\System32  !   OK    ! 9.0a 64bit       ! 10 Pro x64 Version 1607 (Build 14393.693) !
! C:\Windows\SysWOW64  !   NOK   ! 9.0a 64bit       ! 10 Pro x64 Version 1607 (Build 14393.693) !
!----------------------!---------!------------------!-------------------------------------------!
! C:\Windows\System32  !   OK    ! Windows Explorer ! 10 Pro x64 Version 1607 (Build 14393.693) !
! C:\Windows\SysWOW64  !   NOK   ! Windows Explorer ! 10 Pro x64 Version 1607 (Build 14393.693) !
!----------------------!---------!------------------!-------------------------------------------!

C:\WINDOWS\system32\osk.exe	611.328	16.07.2016 13:42	-a--
C:\WINDOWS\SysWOW64\osk.exe	587.776	16.07.2016 13:42	-a--

Regards
Karl

[MVV]

You should start C:\Windows\Sysnative\osk.exe if you're in 32-bit TC under 64-bit Windows.

BTW funny stupid Windows 10, I can start both 32- and 64-bit osk.exe under Windows 7.

[tuska]

You should start C:\Windows\Sysnative\osk.exe if you're in 32-bit TC under 64-bit Windows.

I migrated from Windows 7 Pro to Windows 10 Pro and the folder "Sysnative" did not exist.
Therefore I created this folder and it was filled automatically with files and folders AND
C:\Windows\Sysnative\osk.exe 611.328 16.07.2016 13:42 -a-- ... was there.

But this version of the file does not work and it is not possible to copy/overwrite
from: C:\WINDOWS\system32\osk.exe   611.328   16.07.2016 13:42   -a--
to .. : C:\Windows\Sysnative\osk.exe   587.776   16.07.2016 13:42   -a--

For me it's not a problem though.

EDIT:
The folder "Sysnative" (without creationdate, accessdate) is for me only visible under TC 9.0a 32bit
(and not in TC 9.0a 64bit and Windows Explorer!)

Regards
Karl

[MVV]

Sysnative is a pseudo-folder, a link to real 64-bit System32 folder which is only available in 32-bit programs, so of course Explorer doesn't see it, 32-bit programs also don't see it but can see files and folders in it, and 32-bit TC shows it as a folder because it is possible to enter it.

[tuska]

Thanks for your explanation!

I stay with: http://ghisler.ch/board/viewtopic.php?p=324469#324469
BTW: The folder "Sysnative" is no longer deletable.

Regards
Karl

[MVV]

Yes, you can't delete Sysnative folder because it doesn't exist physically.

Hm, just tried to start C:\Windows\Sysnative\osk.exe, it doesn't work too, it seems that it does something really weird so can't work, it is definitely an osk.exe's bug (Windows 10's osk.exe) that it can't be started from neither of three folders from 32-bit process. It is interesting BTW why I can start osk.exe from either of the folders under Windows 7 correctly while some users can't.

[ghisler(Author)]

Looks like a bug in Windows 10: There is an osk.exe in 32-bit system32, but it doesn't work. Solution: Run the keyboard from the task bar, there is a keyboard icon for that.

[GPEX]

That seems to happen on 64bit OS, when used in a 32bit app. The reason is that it starts the 32bit OSK (in C:\Windows\SysWoW64) instead of the required 64bit one. OSK starts, and then has issues with the OS.

[MVV]

The reason is that it starts the 32bit OSK (in C:\Windows\SysWoW64) instead of the required 64bit one.

It is a well-known fact, however it is a bug in 32-bit osk.exe that it doesn't work in 64-bit Windows 10 (it works fine e.g. in Windows 7).

[HolgerK]

2MVV,

Don't talk with Copy&Paste bots
Original source:
https://www.experts-exchange.com/questions/28524462/How-to-run-osk-exe-in-Windows-System32-folder.html#answer40342341-20

Regards
Holger

[MVV]

HolgerK,
Oh, you're right!
I was able to detect them previously, but this one have loked just as a newbie...