5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH996 Window issue
Reported or suspected cause
microswitch had failed in the door lock motor
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report identifying a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Reported cause
Turned out to be a microswitch had failed in the door lock motor.
Leading evidence: 'microswitch had failed in the door lock motor' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'microswitch had failed in the door lock motor' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Reset but it didn't work' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause · Original poster
I know there is a turbo forum but I suspect my problem is part of the wider 996 world.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
I've tried what I think is the procedure for the window ecu reset but it didn't work for me.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
5 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
I've tried what I think is the procedure for the window ecu reset but it didn't work for me.
Hi guys, that's me back in the world of Porsche after a foray into the supercharged world of AMG (a 2003 S55L) which was a fantastic if somewhat blunt tool. I've now got a 2002 996 Turbo Coupe which is nicely cheese to the S55's chalk! I know there is a turbo forum but I suspect my problem is part of the wider 996 world.
My driver's door window drops a cm to allow the door to open when the handle is pulled, but when the door is open and handle not pulled the window goes back up to it's close position so that if you push the door shut the window stops it from closing and it bounces off the frame. In contrast the passenger side window drops a cm when opened, and stays dropped till it closes again.
If I time it just right, I can hold the door handle open until just before the door closes. If I get it wrong the door just bounces! I've tried what I think is the procedure for the window ecu reset but it didn't work for me.
Any ideas gratefully received!
Cheers
Matt
I just had this exact issue with my car. The window would drop but it would pop back up when the door was opened. I suspected the problem might be the window regulator but is wasn't. Turned out to be a microswitch had failed in the door lock motor. The whole lock motor had to be replaced. Dealer installed:
Part number: 8N1-837-015-C "Drivers Door Lock Motor" $216.00
I didn't want to attempt a DIY on this. With labor it cost $406 at the dealer. It's fixed and working fine now.
As Gary said ^ the window "drop" is controlled by the micro switch in the door handle. I don't think this is a real difficult DIY, but I have not done it personally.
Sounds like the micro switch to me too. If it is the regulator, generally it won't drop down at all or enough to clear the weather stripping when opening.
