10 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHDriver window issue
Leading reported evidence
Run across this
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 · Original poster
Yes, I redid my search and found some more info {my fault for searching on my phone) and ran across this from pfbz
Leading evidence: 'Run across this' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Disconnect battery' (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 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
Is it worth just disconnecting the battery to see if everything resets?
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
Bigger question is should I just replace the regulator while I'm in there
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.
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
Others will have to comment on which window regulator to use, I defer to my Indy on all such matters.
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.
10 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: 20261027T082735Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I recently got my windows tinted and now the driver window is acting a bit strange. It will drop when either interior or exterior handle is pulled, but won't stay down.
I think the installer played with the latch to keep the window up, while he was applying the film. I've looked at the latch and everything seems fine and appears to be working as it should be.
I tried searching but I didn't find anyone having this particular problem. Is it worth just disconnecting the battery to see if everything resets?
thanks
2002 C4S
Yes, I redid my search and found some more info {my fault for searching on my phone) and ran across this from pfbz
Try these tests, see which ones fail:
0) Door open, but latch closed with screwdriver to simulate door being closed. Window should be all the way up.
1) Lightly pull on outer handle (not enough to open latch), window should drop slightly, and return when you let go of the handle.
2) Lightly pull on inner handle (not enough to open latch), window should drop slightly, and return when you let go of the handle.
3) Pull completely on outer handle (enough to open latch), window should drop slightly and stay dropped when you let go of the handle.
4) Reset latch to closed with screwdriver. Window should go back up.
5) Pull completely on inner handle (enough to open latch), window should drop slightly and stay dropped when you let go of the handle.
6) Reset latch to closed with screwdriver. Window should go back up.
So 3 and 5 aren't working for me. And when I put the screwdriver in the latch and jiggled it the window went up and down.
Did you try to "relearn" the windows? Push the down button, then when the window is down continue to hold (push) the button for 10 seconds. Then push the up button and when the window is up continue to hold the button for 10 seconds. That resets the upper and lower limits.
Yeah, i did that as well and it appears to be the same issue. I know the tint guy was saying that he was struggling with the driver window, especially when he flipped the latch. I saw that this morning, before i realized what was going on. Window went crazy up and down and the dome light would come on when driving.
I just don't want to pull the string before I have everything mapped that I want/need to do. Nothing annoys me more when I get into a project and I realize that I need to do something else or in addition to, or that I misdiagnosed the problem.
I appreciate all the help, BTW. thanks to everyone.
This is a source reference. Confirm exact model applicability in the original material.
