8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHTracking down the "window drop" culprit?
Leading reported evidence
Test before i took mine apart
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
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 performed work without a confirmed outcome
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.
Performed · outcome unconfirmed
Also, I have a spare ebay I installed and tested before I took mine apart.
Leading evidence: 'Test before i took mine apart' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is '"door closed sensor" - the sensor in the door' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace things' (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
I think the issue is with your "door closed sensor" - the sensor in the door that can tell if the door is completely shut or not.
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
The fact that bumps trigger the window drop and reset suggests a loose connection somewhere else, which leads me to suspect the door latch.
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 don't particularly want to start throwing money away replacing things that may not need to be replaced, but certainly do want to get this sorted.
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
The fact that bumps trigger the window drop and reset suggests a loose connection somewhere else, which leads me to suspect the door latch.
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.
8 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.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T020439Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I've reviewed as many threads as I can find on this issue but I haven't really figured out how to identify the actual culprit behind my window drop issue. I've spoken with the team at Pelican Parts and have seen as many Youtube videos as I can find but I haven't figured out how to specifically trace down the specific cause of my window drop problem. Here are the symptoms/conditions:
Pull the inside door handle, the window drops as it should but then pops back up to the "closed" position when I let go, even though the door is still open. I have to hold the handle pulled toward me to close the door and then release it when the door shuts.
Pull the outside door handle, I get the same result.
When driving down the road (yes, with the door closed), the window will sometimes drop when I hit a bump. I hit another bump and it pops back up to the closed position. Bump -> down. Bump again -> up. Rinse and repeat
ad nauseum.
I've learned that at least three different components can cause window drop issues. I'm hoping the pool of experience here can help me track down the culprit between 1) the inside handle microswitch, 2) the outside microswitch, 3) the door latch mechanism, or ...) some other component/culprit. The fact that the inside door handle and the outside door handle (mal-)function the same way suggests it may not be a microswitch, unless both of them are problematic. The fact that bumps trigger the window drop and reset suggests a loose connection somewhere else, which leads me to suspect the door latch.
Thoughts on this? I don't particularly want to start throwing money away replacing things that may not need to be replaced, but certainly do want to get this sorted. Are there any test procedures I could try to narrow down the source of the window drop problem?
As ever, thanks for the experience and wisdom.
I agree with you and the going over bumps thing had me thinking about your microswitches and sensors also. I think the issue is with your "door closed sensor" - the sensor in the door that can tell if the door is completely shut or not. When I looked this up I found this thread about a 996 Turbo from 2010 that sounds like this part could cause your issue.
https://www.renntech.org/topic/32406...closed-sensor/
My guess would be the latch. The solder joints from the circuit board to the connector crack and cause weird intermittent problems. You may not be able to see this with the naked eye
Many thanks. I was able to also reach Chris Amond, the PCA guru on the 996. I described the conditions to him and he also diagnosed the latch instead of the microswitches. Part ordered from Porsche Delaware today for $367 shipped. Part # 9A7-837-015-03.
you can fix it easily....for free. Also, I have a spare ebay I installed and tested before I took mine apart. I'll send it to you. you install it and verify it works and send me 100 bucks
This is a source reference. Confirm exact model applicability in the original material.
