Bad Vista Experiences?
 Published by Chris123NT on Wednesday, October 3rd, 2007 at 11:50 pm
 This publication is filed under Windows Vista

So for the past few days I’ve been reading some forum posts which seem to have a common theme.  People are having some pretty bad experiences with Vista.  These range anywhere from minor annoyances to driver issues that completely hose the system.  So this all got me thinking, since SP1 is in beta, we can bug all of these things and MAYBE Microsoft will wake up and realize that some of this stuff needs to be fixed.

So this is where you, the readers of this blog, come in.  Make a comment to this post and discuss any of your bad experiences with Vista and I will make sure these issues are forwarded to the right people to have the best chance of getting fixed.  Have at it, and I look forward to reading all of the responses!

Comments RSS Feed
Chris123NT says:

Test Comment, making sure commenting is working.


Trevor Williamson says:

I really like Vista but the Nvidia drivers suck…SUCK, SUCK, SUCK…I am so tired of driver shutting down blah blah blah…

…am\nd why does it take so long for IE to open? And the Network stuff is taking longer…why did I say I really liked Vista?


Kandarp says:

So far I love Vista. Have not had any problems. IE used to crash. But that was due to a bad plugin that I uninstalled.


Ciprian says:

Hello,

We have run a similar poll/analysis on our site. You can see the results and the comments of our readers here:
http://www.vista4beginners.com/Windows-Vista-problems

My biggest issue is with IE 7 Add-ons. The available offerings are really bad and some of them are even a security risk. You can read more here:
http://www.vista4beginners.com/Top-10-Reasons-Why-Internet-Explorer-7-Add-Ons-Suck


Ryan says:

You’d really do that for us, Chris? All right then, I’ll take your word for it.

Unless I’m not aware of something, it should not matter what drive you install whatever versions of Windows if you do a dual boot. I all ready know you want to install the older one first, and then the newest. What I mean is, I used to have an installation setup that had XP Pro on a D:\, but when I installed the Vista service pack beta onto the C:\ (the one that was a full image) if messed up my XP Pro install and I ended up reformatting. The XP install and boot was gone. Something got hosed relating to booting and I could not get it recovered.


Mark says:

Anyone suffering from painfully slow start up in Vista? Have been trying to sort it to no avail. Can anyone give a solution to this problem as its taking 3-4 mins to boot up.

Running Vista Home Premium
Core 2 T7300 2Ghz
2 GB RAM


Ross Snowden says:

One thing that may help (if not only for the placebo-effect), make sure that in the system configuration utility under the tab: “boot” in the advanced options you should make sure that “Number of Processors” is selected and the pull-down option is set to “2″. This way, your machine will boot using the both cores of the processor.


David says:

Mark says:

Thanks for the advice, unfortunately still got no joy rectifying the problem. Was flicking through my “System Information” and found the my 6TO4 adapter drivers apparently aren’t loading so its listed under “Problem devices”. Could this be causing slow boot up? Had a look on tinterweb and it seems the 6TO4 seems to be a common problem. Any chance the could be a relevent problem for Microsoft to address Chris?


Chris123NT says:

Mark, can you post the error that’s recorded in the event log due to the driver not loading? Thanks.


Mark says:

Yer no prob, been searching through the logs and this seems to be the only thing I can find to directly refernce the problem. Please let me know if this is what you require, if not I shall try and look for more info for you.

Mark

6T04 adapter properties.
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)


Mark says:

PS. could this be the cause of why my system takes so long to start up? Going to try and perform clean boot procedure to see if I can isolate the problem http://support.microsoft.com/kb/331796 just have to find the time to do it now unless anyone can offer any suggestions. Thanks for everyones time :)


Mark says:

Hello to all,

Just an update on my Vista Boot problems (not that anyone is probably interested but here I go lol!) Found that the problem seems to lie with the User Account Control (UAC). As soon as I switched this off my machine booted up straight away. No more black screen of death for 3 minutes! Just to make sure I switched it back on, the boot problem reappeared ….. switched UAC off, the boot problem went away!

Any chance this incident could be flagged to Microsoft Chris? Could be a wider problem that needs to be addressed.

Cheers
Mark


Chris123NT says:

Mark,

Yes this problem appears to be an incompatibility with UAC so if you could e-mail me with all the details you can think of I will send this off to MS. I need as much detail as possible so they don’t just sit there and go “No Repro”.


Mark says:

Please let me know if you think I’ve missed information that could be vital. Thanks Mark :)

UAC-FileVirtualization

Failed to set up the instance for a volume.
+ System
- Provider
[ Name] Microsoft-Windows-UAC-FileVirtualization
[ Guid] {c02afc2b-e24e-4449-ad76-bcc2c2575ead}

EventID 2005

Version 0

Level 2

Task 0

Opcode 0

Keywords 0×8000000000000000

- TimeCreated
[ SystemTime] 2007-05-17T07:19:18.945Z

EventRecordID 1

Correlation

- Execution
[ ProcessID] 4
[ ThreadID] 52

Channel Microsoft-Windows-UAC-FileVirtualization/Operational

Computer LH-JJMAZ2ABERMQ

- Security
[ UserID] S-1-5-18

- EventData
Error 3221226140

UAC – Operational (3 entries as below)

The process failed to handle ERROR_ELEVATION_REQUIRED during the creation of a child process.

Diagnosis –DPS (Just some of the entries in this log (too many to list all), all errors seem to point to pcadm.dll)

Diagnostic module {50E3B0EB-5780-49DE-9EB5-8D53A51FD146} (%windir%\system32\pcadm.dll) encountered an error while handling scenario {D113E4AA-2D07-41B1-8D9B-C065194A791D}, instance {C5964515-90DA-4453-B829-AC8FE0EB2789}, original activity ID {00000000-0000-0000-0000-000000000000}. The error code was -2147467259.
+ System
- Provider
[ Name] Microsoft-Windows-Diagnosis-DPS
[ Guid] {6bba3851-2c7e-4dea-8f54-31e5afd029e3}

EventID 170

Version 0

Level 2

Task 1

Opcode 21

Keywords 0×4000000800000000

- TimeCreated
[ SystemTime] 2007-10-21T16:57:20.487Z

EventRecordID 1162

- Correlation
[ ActivityID] {C5964515-90DA-4453-B829-AC8FE0EB2789}

- Execution
[ ProcessID] 1640
[ ThreadID] 2620

Channel Microsoft-Windows-Diagnosis-DPS/Operational

Computer Mark-PC

- Security
[ UserID] S-1-5-19

- EventData
ScenarioId {D113E4AA-2D07-41B1-8D9B-C065194A791D}
InstanceId {C5964515-90DA-4453-B829-AC8FE0EB2789}
OriginalActivityId {00000000-0000-0000-0000-000000000000}
DiagnosticModuleImageName %windir%\system32\pcadm.dll
StatusCode -2147467259
DiagnosticModuleId {50E3B0EB-5780-49DE-9EB5-8D53A51FD146}

Diagnostic module {50E3B0EB-5780-49DE-9EB5-8D53A51FD146} (%windir%\system32\pcadm.dll) encountered an error while handling scenario {D113E4AA-2D07-41B1-8D9B-C065194A791D}, instance {1EC507E9-C886-43E5-8ED1-22E2EF0FC919}, original activity ID {00000000-0000-0000-0000-000000000000}. The error code was -2147467259.
+ System
- Provider
[ Name] Microsoft-Windows-Diagnosis-DPS
[ Guid] {6bba3851-2c7e-4dea-8f54-31e5afd029e3}

EventID 170

Version 0

Level 2

Task 1

Opcode 21

Keywords 0×4000000800000000

- TimeCreated
[ SystemTime] 2007-10-21T16:57:20.487Z

EventRecordID 1161

- Correlation
[ ActivityID] {1EC507E9-C886-43E5-8ED1-22E2EF0FC919}

- Execution
[ ProcessID] 1640
[ ThreadID] 2600

Channel Microsoft-Windows-Diagnosis-DPS/Operational

Computer Mark-PC

- Security
[ UserID] S-1-5-19

- EventData
ScenarioId {D113E4AA-2D07-41B1-8D9B-C065194A791D}
InstanceId {1EC507E9-C886-43E5-8ED1-22E2EF0FC919}
OriginalActivityId {00000000-0000-0000-0000-000000000000}
DiagnosticModuleImageName %windir%\system32\pcadm.dll
StatusCode -2147467259
DiagnosticModuleId {50E3B0EB-5780-49DE-9EB5-8D53A51FD146}

Diagnostic module {50E3B0EB-5780-49DE-9EB5-8D53A51FD146} (%windir%\system32\pcadm.dll) encountered an error while handling scenario {D113E4AA-2D07-41B1-8D9B-C065194A791D}, instance {10A5FCA6-D5BB-441F-97D4-76BD9223AFF1}, original activity ID {00000000-0000-0000-0000-000000000000}. The error code was -2147467259.
+ System
- Provider
[ Name] Microsoft-Windows-Diagnosis-DPS
[ Guid] {6bba3851-2c7e-4dea-8f54-31e5afd029e3}

EventID 170

Version 0

Level 2

Task 1

Opcode 21

Keywords 0×4000000800000000

- TimeCreated
[ SystemTime] 2007-10-21T16:57:20.487Z

EventRecordID 1160

- Correlation
[ ActivityID] {10A5FCA6-D5BB-441F-97D4-76BD9223AFF1}

- Execution
[ ProcessID] 1640
[ ThreadID] 2608

Channel Microsoft-Windows-Diagnosis-DPS/Operational

Computer Mark-PC

- Security
[ UserID] S-1-5-19

- EventData
ScenarioId {D113E4AA-2D07-41B1-8D9B-C065194A791D}
InstanceId {10A5FCA6-D5BB-441F-97D4-76BD9223AFF1}
OriginalActivityId {00000000-0000-0000-0000-000000000000}
DiagnosticModuleImageName %windir%\system32\pcadm.dll
StatusCode -2147467259
DiagnosticModuleId {50E3B0EB-5780-49DE-9EB5-8D53A51FD146}

Diagnostic module {50E3B0EB-5780-49DE-9EB5-8D53A51FD146} (%windir%\system32\pcadm.dll) encountered an error while handling scenario {D113E4AA-2D07-41B1-8D9B-C065194A791D}, instance {985FD1B4-C4A6-408F-A236-F6798F90B728}, original activity ID {00000000-0000-0000-0000-000000000000}. The error code was -2147467259.
+ System
- Provider
[ Name] Microsoft-Windows-Diagnosis-DPS
[ Guid] {6bba3851-2c7e-4dea-8f54-31e5afd029e3}

EventID 170

Version 0

Level 2

Task 1

Opcode 21

Keywords 0×4000000800000000

- TimeCreated
[ SystemTime] 2007-10-21T16:57:20.487Z

EventRecordID 1159

- Correlation
[ ActivityID] {985FD1B4-C4A6-408F-A236-F6798F90B728}

- Execution
[ ProcessID] 1640
[ ThreadID] 2616

Channel Microsoft-Windows-Diagnosis-DPS/Operational

Computer Mark-PC

- Security
[ UserID] S-1-5-19

- EventData
ScenarioId {D113E4AA-2D07-41B1-8D9B-C065194A791D}
InstanceId {985FD1B4-C4A6-408F-A236-F6798F90B728}
OriginalActivityId {00000000-0000-0000-0000-000000000000}
DiagnosticModuleImageName %windir%\system32\pcadm.dll
StatusCode -2147467259
DiagnosticModuleId {50E3B0EB-5780-49DE-9EB5-8D53A51FD146}


Loek says:

When I try to get the performance scores I get the same messages as above: EventID 170, error code -2147467259. Please let me know if there is a solution.


Kris Scott says:

Wireless networking needs a major overhaul. I connect to my campus’ wireless network and vista makes a new connection for each AP I’m connected to, so I have Wireless connection [1-8] in my vista right now, all for the same network.

Networking in general needs improvements too, in XP I could easily release/renew my ip if needed, with vista the repair operation takes forever.


Jay P says:

I have an HP Laser jet 1012. sometimes the print drivers work, sometimes they dont, I even tried the 1015 drivers and still get marginal results. Sometimes it even crashes the print spooler.


Randall says:

What can I say…. I’m running Vista in my new laptop and had this friggin error code since day 1 6to4 code 10…… Office 2007 doesn`t work properly, can`t even register the product, Multimedia centre keeps crashing and Norton quit a few days ago and the weather gadget just quit working….. I`ve even tried removing hardware and reinstalling drivers but to no avail…… What the frigg
I`m ready to wipe the system and go with Linux…. The laptop is an Acer 5520, nice little computer….
Any solutions? randalltrenholm@hotmail.com


Vista says:

Vista isn’t racist enough for me. Too PC.


Abhishek Srivastava says:

I have an Lenovo Y500 series laptop with Windows Vista installed. In the Device Drivers, under Network Adapters, there is a device named 6T04 Adapter and it has the yellow exclamation point by it. When I try to update the driver it tells me that it already has the latest driver loaded.

What is this thing, and why won’t it work?

Should i uninstall this or not?
If Yes then how will i get it back?



This design is not to be copied, reproduced, or modified in any way by 3rd parties.
Exclusively designed for chris123nt.com only. THIS THEME IS COPYRIGHTED WORK, AND IS NOT TO BE REPRODUCED UNDER ANY CIRCUMSTANCES. Designed by Kristan M. Kenney, http://www.chris123nt.com EXCLUSIVELY FOR chris123nt.com