Jhon
Posts:35
 |
| 05/06/2008 9:24 AM |
|
In the effort to have the most common error/help requests addressed, please read below from Ncomputings website:
+++++
Incompatible Module win32k.sys / MS update KB941693 Incompatibility
Although this error message may or may not affect our product functionality it will continually prompt you with this "Module" error whenever the system starts up.
To remove this error message, you have to uninstall the Microsoft Security update "KB941693" through add/remove programs in the Control Panel. Make sure you select "Show updates", scroll to the "KB941693" update and hit "remove". It will prompt you stating that other updates may be dependent on this update. Disregard this, and finish the removal. the system will need to be restart and the update should be successfully removed. Make sure you turn off Auto installation of updates through "Automatic Updates" so that the update will not be reinstalled inadvertently.
Se detailed instructions in the attached file.
+++++
Since the new board doesn't appear to allow links or attachments (lovely upgrade), here's the link to the attached file:
http://na3.salesforce.com/servlet/servlet.FileDownloadPkb?file=00P50000002N8Fp&orgId=00D500000006uQp&pPid=50150000000Hx1C
|
|
|
|
|
stone
Posts:8
|
| 05/06/2008 11:05 PM |
|
** The release notes of 4.03.091 say "Compatibility with Microsoft Update "KB941693" is included in this release." **
But....I have try to install the 4.03.091, the "win32k.sys 0x00000140" error message still happen on each time the officestation logon the host pc!
Anyone can help me? |
|
|
|
|
kkawasaki
Posts:0
|
| 05/08/2008 8:28 PM |
|
I met same issue after installing windowsXP SP3.
The release notes of 4.03.091 say support SP3 RC2.
But, it isn't working correctly with released SP3.
After uninstalling SP3, the host PC works neatly.
Did someone install 4.03.91 with SP3? and work it?
The other host PC that not installed SP3 is working with 4.03.091.
|
|
|
|
|
alank
Posts:2
|
| 05/13/2008 8:38 PM |
|
Same problem here. Did a clean install of XP. Installed SP3. Installed NCT-2000-XP 4.03.091. Get win32k.sys 0x00000140 error. It does not prevent anything from working. Just annoying. Cannot remove KB941693 because it was bundled in SP3 so it's not listed in Add/Remove Programs. I do not understand why they say .091 is compatible with KB941693. I hope someone will figure this out soon. I guess the workaround is to clean install XP again and only install SP2. Then use Windows Update to get all the patches, including KB941693, then go in and remove KB941693. What a pain. |
|
|
|
|
rshingala
Posts:11
|
| 05/19/2008 12:15 AM |
|
I have installed 4.03.091 in Win2003 Server, problem of Win32k.sys was resolved.
Make sure to unistall 4.03.090 before you install new version. It will resolve your problem.
Rajesh Shingala
SIS |
|
|
|
|
ahill
Posts:7
|
| 05/19/2008 11:55 AM |
|
That is on a Win2k3 system. Different OS then Win XP. Yes the latest NCT software is stable under Win2k3, but not Windows XP (with all updates; specifically the ones mentioned above which includes SP3). If you installed Win XP SP3 I suggest removing it and installing individual updates excluding the one mentioned in this thread.
Oh an this new forum software is terrible... |
|
|
|
|
tnt
Posts:1
|
| 05/22/2008 4:06 PM |
|
Removing the update is a bad idea. This update stops one way someone may hijack a windows session... It's better to deal with the error (which does not hinder operation) untill NComputing releases a patch. |
|
|
|
|
Aubry
Posts:26
|
| 05/23/2008 11:25 AM |
|
There is some ambiguity as to the different causes of this "win32k.sys" error message, and I would like to try and clear some of that up. In a nutshell, this error is caused when the version of the Windows system file "win32k.sys" has a version number higher than that listed in our software as being compatible. Thus, this error can be caused by any Windows update that increments the win32k.sys file version, and does not necesarily indicate a loss of functionality. KB941693 and SP3 are two such updates.
Version 4.03.090 of the NCT-2000-XP software will throw this error with KB941693, and will not function with SP3 installed.
Version 4.03.091 of the NCT-2000-XP software does not throw the error with KB941693, and functions in SP3 (but throws the win32k.sys error).
The next release of the NCT-2000-XP software is expected to eliminate this message entirely, up to the file version included in SP3.
In general, it is recommended that you turn off automatic updates, and test every software update in an isolated environment before deploying it system-wide. |
|
|
|
|
alank
Posts:2
|
| 05/31/2008 9:56 PM |
|
| Version 4.03.094 has fixed this. |
|
|
|
|
cavaco
Posts:3
|
| 07/01/2008 2:39 AM |
|
Posted By alank on 05/31/2008 9:56 PM
Version 4.03.094 has fixed this.
Hi!
And where can we donwload that version? |
|
|
|
|
USD412Tech
Posts:24
|
| 07/13/2008 4:29 AM |
|
You will have to use the supplied Internet Update.
Start Menu > All Programs > NCT-2000-XP > NCT-2000-XP Internet Update
You will be prompted to register if you have not already. |
|
|
|
|
BrianKline
Posts:1
|
| 09/16/2008 10:37 AM |
|
There's a problem with trying to run the internet update. It asks for me to register, but I cannot complete the registration, therefore I'm unable to update the software. I click "Register Now", enter the password I assigned, enter all my information, select online registration, and the next window shows no serial numbers under "your serial number list". Why should I have to enter serial numbers for L230's that aren't even connected to this computer? We have L230's, but they're connected to other computers and have already been registered. Furthermore, why would the L230's on my network not show up? Possibly because of the win32k.sys error message that comes up when I log into this machine? This may be one of the most rediculous registration processes I've ever had to go through. The software doesn't work, the thin clients can't connect to this computer, and the fix is to update the software, and to update the software you need the thin clients to connect to this computer that can't connect because the software doesn't work.
This is the fourth installation of this software I've gone through now, and 3 of those times I've run into this problem. For whatever reason, one of those installations went off without a hitch. Every time I get this error, I come here hoping there's a fix, but what you list for a fix never works. I think my company is going to be looking into Wyse terminals very soon. I've waited 6 months now and no real fix has been offered by Ncomputing.
Please, if you do come up with a fix for this problem, or you have software you can send me, please e-mail me.
|
|
|
|
|
hjkcga
Posts:165
|
| 09/16/2008 12:15 PM |
|
Download from the instalation that is working and ensure that you save the update. They are quite small and will fit on a thumb drive. This way you could transfer it to the other two machines.
To save update click on options in the NCT-2000-XP Update Service.
Also, this is still only a user board. If you are having problems that are not being solved here, I would contact Ncomputing directly. |
|
|
|
|
ondeda
Posts:26
|
| 09/22/2008 4:18 AM |
|
| has any one tried installing the new version of V97 and used it to prevent the error message from displaying |
|
|
|
|
Metria
Posts:10
|
| 09/22/2008 9:31 AM |
|
I am running V97 without a problem... Updated last week.
|
|
|
|
|
palmeida
Posts:2
|
| 10/14/2008 5:58 PM |
|
I noticed today that the KB954211 update causes the same problem.
To remove this error message, you have to uninstall the Microsoft Security update "KB954211" through add/remove programs in the Control Panel. Make sure you select "Show updates", scroll to the "KB941693" update and hit "remove". Reboot the computer.
|
|
|
|
|
farmeunit
Posts:1
|
| 10/15/2008 5:49 PM |
|
Is it really that hard to have a fix for the win32k.sys quickly after MS releases a patch? I'm getting the same error on a Win2k machine after running the updates, then installing the X300. I did uninstall the KB94163 update, which worked, but there should be a more proactive approach from NComputing for take care of this problem.
I am using the newest drivers as of 10-15-08. |
|
|
|
|
lyndesc
Posts:2
|
| 10/20/2008 8:48 AM |
|
I'm getting this "cosmetic" error, every login on the host machine. I have X300 (20 of them) running version 4.3.98 of the ncomputing software. They are all XP SP3 fully patched. They are all members of our domain, so uninstalling - reinstalling the ncomputing software is an issue (we already had to do that to get the computers work with the ncomputing software).
This error means that anything that happens while the kids are using the computer is blaimed on this error. People see it when they log on and assume something is broken.
Not so good.
Craig Lyndes
Franklin Central SU |
|
|
|
|
freshairstudios
Posts:2
|
| 10/21/2008 12:07 PM |
|
Our XP terminal server has recently updated to SP3. We started to get the incompatible win32k.sys error. So updated to the latest version currently available of the server software accordingly. That fixed it for a while.
Until yesterday morning that is.
It now appears another update has thrown out the win32k.sys. Unfortunately, all efforts to roll back the machine to pre-SP3 OR manually uninstall the KB954211 or KB941693 updates (as suggested in theknowledge base earlier) hasn't quite worked.
Have reinstalled the latest server software.
The current situation is: We don't get the win32k.sys error any more, but when you log-in on a terminal it freezes the whole machine. Uninstalling the server software restores the machine to normal.
I am now left with an entire office unable to work... and a machine that doesn't want to roll back.
Does anyone have any ideas?
|
|
|
|
|
hjkcga
Posts:165
|
| 10/22/2008 12:30 PM |
|
freshairstudios
You do not need to roll back to SP2. The latest software from Ncomputing is SP3 compatible. You should never have the windows automatic updates turned on in these systems. Only update when you have time to check that the system will work. You need to get you system back to last week. What about a backup? |
|
|
|
|