8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPassenger window help
Leading reported evidence
Install so had no come back
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
I self installed so had no come back on warranty, annoying because it wasn't that cheap.
Leading evidence: 'Install so had no come back' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'window regulator issue' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check (quite wet, turns out ive lost the door bung!)' (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 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
sounds like the membrane seal is also leaking.....as per recent posts on this; I used some self adhesive rubber strip to repair mine when it went
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.
Check (quite wet, turns out ive lost the door bung!)
Suggestion or failed attempt
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 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 removed the door card to check (quite wet, turns out Ive lost the door bung!)
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
I would recommend speaking to local OPC and buying a genuine part (PCGB discount helps!).
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.
911uk: 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: 20261026T063944Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi all
Today when reversing I rollowed the passenger window down and started getting what appeared to be a crunching noise. I couldn't quite here so went back and forth a couple of times to confirm.
It now doesnt go down or up and I have had to manually pull the window up to keep it shut.
I've removed the door card to check (quite wet, turns out Ive lost the door bung!)
I can't see the regulator or or window behind the frame so can't work out what the issue is..... however, when rolling the window down (the wire is very loose and perhaps not connected properly?
Can anyone advise what the issue is?
Many thanks
Mine did the same last summer; the regulator cable had snapped. Not too difficult to strip the door down to replace, plenty of guides & videos online. One thing I learnt from it was that most of the cheaper (generic) non-OEM replacement parts are not actually equivalent as they are missing the section that allows you to add extra tension to the cable, which seems important for the 1cm drop when opening the door. The one from ECP has this so I used that in the end (after trying a variety of others), but tbh I wish I’d just gone straight for the slightly more expensive OEM item.
Definitely sounds like the regulator - I bought an ebay unit which whilst being described as good quality, was terrible and broke in months. I self installed so had no come back on warranty, annoying because it wasn't that cheap. I would recommend speaking to local OPC and buying a genuine part (PCGB discount helps!).
That's really helpful thank you!
The bottom of the door carpet is now getting wet (Which is sort of odd, as the widow is pushed to the top with no gap and seals new)
Any thoughts, or will a new regulator sort this issue?
Thanks again
