2004 Pontiac Vibe visibility problems

Filed Sep 27, 2019 · Visibility · 210,000 miles · MN

Tl* the contact owns a 2004 pontiac vibe. While the vehicle was idling with the rear defroster activated, the rear hatch window shattered. The vehicle was taken to lupient buick/gmc (7100 wayzata blvd, golden valley, mn 55426) where it was currently being diagnosed. The manufacturer was notified of the failure and provided case number: 9-5481767211. The vehicle was not repaired. The approximate failure mileage was 210,000.

Filed Aug 8, 2018 · Body, Visibility · 95,500 miles · IA

Tl* the contact owns a 2004 pontiac vibe. While the front driver's side window was going down, a clunking sound was heard. The vehicle was taken to the local dealer (h&h buick, 3400 s. Expressway st., council bluffs, ia, 844‑879‑6715) where it was diagnosed that the window regulator was faulty and needed to be replaced. The vehicle was not repaired. The manufacturer was notified of the failure, but no assistance was offered. The failure mileage was 95,500. *tt consumer stated the previous recall notice was accomplished in may of 2017 but window problems were present after that was done. The dealer replaced the window regulator but it did not solve the problem. My drivers side still clunks when window is rolled down and it sounds like window could break at some point, this should not happen and is danderous. Replacing the belts on the original recall worked for a time but it came back. I was told a new regulator for the window would solve the problem. After window regulator was replaced the clunking sound still happens. Updated 10/18/18

Filed Mar 18, 2018 · Body, Visibility · 103,000 miles · IL

Hood latch failed at highway speeds allowing the hood to open and bend backwards, breaking windshield, fully obstructing driver's view, and damaging the roof of the vehicle as well as the hood, hinges, and body panels

Filed Sep 3, 2017 · Visibility · PA

Driver side window is sticking and make erratic movement going up and appears to not be tracking correctly. This car has been owned by same family since new in 2004 and this issue has been noticeable for some time now. Passenger side is slow in coming up I found gm recall #07273 came up online under visibility recall service bulletin 08v162000 dated 04/10/08 and wondered if this was a cause.

Filed Nov 12, 2015 · Visibility · 100,313 miles · MI

Driving home two nights ago through the city and the driver's side window wouldn't roll up and almost broke. It is loose of the regulator and out of the track. Once I got home, I had to remove side panel to get it back in the guide in order to close it. Still broken. Gm/pontiac says it is not within the assigned recall vins. But it is the exact same issue!

Filed Oct 19, 2015 · Visibility · 188,000 miles · NC · 1 injury

Tl* the contact owns a 2004 pontiac vibe. While closing the driver side window, the window shattered without warning and the pieces struck the contact's face. The contact stated that pieces of glass stuck to her face and required medical attention. The manufacturer was notified of the failure. The vehicle was not diagnosed or repaired. The failure mileage was 188,000.

Filed Mar 30, 2015 · Visibility · 250,000 miles · MD

On may 2, 2015 my wife told me the window got loose and shattered while trying to raise it with the power window. I called the dealer and there is a recall number 07273 on the regulator bolts getting loose and the glass shattering. I called the dealer and talked to [xxx] at winegardner gm in brandywine, md and they said they would charge me for a diagnostic if the fix the recall. I called the gm corporate engagement center at gm with [xxx] at 866‑790‑5700 ext. [xxx] and complained and he also said I would have to pay to get a diagnostic for them to fix the recall. I called customer care [xxx] customer relations 866‑418‑9319 ext. [xxx] and spoke to [xxx] and she said a diagnostic has to be done and I would be charged by gm for the diagnostic. My VIN is [xxx]and my recall is not being fixed. This is the second time the window shattered because of this recall. Information redacted pursuant to the freedom of information act (foia), 5 u.s.c. 552(b)(6).

Filed Nov 14, 2014 · Airbags, Visibility · LA

Tl* the contact owns a 2004 pontiac vibe. The contact received notifications for the federal safety agency campaign number: 14v655000 (air bags), the federal safety agency campaign number: 13v029000 (air bags), and the federal safety agency campaign number: 08v162000 (visibility). However, the parts needed were not available. The dealer was contacted and was unable to provide a timeframe for when the part would become available. The manufacturer was notified. The contact was waiting for parts. The contact had not experienced a failure.

Filed Aug 13, 2014 · Visibility · 100,000 miles · MA

Tl* the contact owns a 2004 pontiac vibe. The contact stated that the driver side window regulator mechanism failed. In addition, the driver side window made an abnormal noise, contained a deep, horizontal crack, and was becoming off track. The VIN was not included in the federal safety agency campaign number: 08v162000 (visibility). The manufacturer was made aware of the failure. The vehicle was not repaired. The approximate failure mileage was 100,000.

Filed Aug 9, 2014 · Visibility · 93,216 miles · WI · 1 injury

Car was in park when I was in the process of putting down the driver side electric window. When it was going down it made a loud noise and then stopped going down any further. At this point it was about 3/4 of the way down and the window was now at a slant. It allowed me to put it back up, but in the process of the window going up it shattered. The majority of the broken window was on me and the front seat of the car. Luckily the car was in park when it happened and I only has a few cuts on my legs from the broken window. In 2008 I had the car in for a recall to replace bolts to both of the front window regulators, mileage at this time was 47,000. The gm dealer I took the car into to have the window replaced, informed me that I need to have the regulator and run channel replaced.