Free Republic
Browse · Search
General/Chat
Topics · Post Article

Skip to comments.

Vista's long goodbye - Deleting files can take forever
The Register ^ | 03/26/2007 | Dan Goodin

Posted on 03/27/2007 7:25:57 PM PDT by Swordmaker

Windows Vista suffers from a bug that causes many machines to stall while deleting, copying and moving files, a flaw that has provoked consternation in online forums.

"I've seen this bug in action, and trust me, it's as if you're copying over a 64k link using only 256mb of RAM," one Reg reader complained. "To add to the problem, you can't cancel or anything."

According to a thread on Microsoft's TechNet site, Microsoft has issued a hotfix for the problem, but it has failed to quell the outrage. For one thing, individual users must get Microsoft's approval before the fix can be downloaded, according to our tipster. And for another, hotfixes are more of a pain to install than patches.

We've contacted a Microsoft spokeswoman, who promised to see if a patch for the problem (is) in the works. Meanwhile, Vista users continue to grumble.

"I simply can not believe that I updated to a new computer and put windows Vista on it to find that it's not even capable of moving and deleting files in an efficient manner," one disaffected user posted in the Microsoft forum. "Microsoft must be kidding! The most basic of features that I use all the time is a slow train wreck." ®


TOPICS: Business/Economy; Computers/Internet
KEYWORDS: microsoft; pctech; vista; windows
Navigation: use the links below to view more comments.
first previous 1-2021-4041-54 next last
To: CedarDave

There is a program called cachemanXP that is much better than those FreeRam programs that just send RAM to swap files.


21 posted on 03/28/2007 12:31:42 PM PDT by JerseyHighlander
[ Post Reply | Private Reply | To 11 | View Replies]

To: CedarDave
I was wondering if any of you have used a program called "FreeRAM XP Pro" to free up that RAM or have any other suggestions.

Though I have scads of RAM on my systems, I do use a program called RamBooster that runs resident and will optimize RAM when available RAM gets below a certain level. It has been very helpful at times of heavy system usage.

22 posted on 03/28/2007 12:32:04 PM PDT by Bloody Sam Roberts (Don't question faith. Don't answer lies.)
[ Post Reply | Private Reply | To 11 | View Replies]

To: LibreOuMort

ping


23 posted on 03/28/2007 3:18:38 PM PDT by sionnsar (?trad-anglican.faithweb.com?|Iran Azadi| 5yst3m 0wn3d - it's N0t Y0ur5 (SONY) | UN: Useless Nations)
[ Post Reply | Private Reply | To 1 | View Replies]

To: Bloody Sam Roberts
I have been having this problem with my WinXP for some time now.

I was "upgraded" to XP a few weeks back. It started exhibiting this behavior just today.

24 posted on 03/28/2007 3:20:12 PM PDT by sionnsar (?trad-anglican.faithweb.com?|Iran Azadi| 5yst3m 0wn3d - it's N0t Y0ur5 (SONY) | UN: Useless Nations)
[ Post Reply | Private Reply | To 6 | View Replies]

To: sionnsar

Well... can't blame Microsoft for a failing mouse. Task Manageer was a big help here.


25 posted on 03/28/2007 3:29:49 PM PDT by sionnsar (?trad-anglican.faithweb.com?|Iran Azadi| 5yst3m 0wn3d - it's N0t Y0ur5 (SONY) | UN: Useless Nations)
[ Post Reply | Private Reply | To 24 | View Replies]

To: Turbopilot; JerseyHighlander; Bloody Sam Roberts; SamAdams76; Swordmaker; KoRn

O.k. System locked up again last night. Had the CPU info minimized so was able to see the problem. The offender was msmsg.exe [MS Messenger? I don't use that to my knowledge]. I ended that process but was still at 99% CPU with explorer.exe being the culprit. I ended that and the screen went blue so had to reboot anyway.

Suggestions, please.


26 posted on 03/30/2007 7:22:02 AM PDT by CedarDave
[ Post Reply | Private Reply | To 16 | View Replies]

To: CedarDave

Add/Remove programs, Add/Remove Windows Components, and uncheck messenger on the list, follow the wizard that will start up to remove it.

I would also go into Control Panel, Administrative Tools and then Services. Find it if its still on the list and right click on it, select properties, click the drop down and change its status to disabled.


27 posted on 03/30/2007 7:26:52 AM PDT by KoRn (FRED THOMPSON FOR PRESIDENT!)
[ Post Reply | Private Reply | To 26 | View Replies]

To: CedarDave

PS: Those instructions only apply to Windows XP SP1. Earlier versions require some registry hacks.


28 posted on 03/30/2007 7:28:15 AM PDT by KoRn (FRED THOMPSON FOR PRESIDENT!)
[ Post Reply | Private Reply | To 26 | View Replies]

To: CedarDave

Actually XP SP1 and later.

/slaps self


29 posted on 03/30/2007 7:29:23 AM PDT by KoRn (FRED THOMPSON FOR PRESIDENT!)
[ Post Reply | Private Reply | To 26 | View Replies]

To: CedarDave
KoRn's suggestion to get rid of MS Messenger was a good one, assuming you don't use it. Here are the directions from Microsoft to ensure you have it disabled and prevented from starting automatically. It may be trying to access a network and locking the system until it finds one.

If you disable the network, come back and find the system hung, what happens if you reenable the network? Does the system unfreeze or does it continue to stay stuck?

30 posted on 03/30/2007 7:58:54 AM PDT by Turbopilot (iumop ap!sdn w,I 'aw dlaH)
[ Post Reply | Private Reply | To 26 | View Replies]

To: CedarDave; KoRn
The offender was msmsg.exe

I use a little utility called XP Anti Spy right after installing Winders XP.

It lets you shut off all the "phone home" settings as well as those "balloon tips", error reports, remote desktop and a host of other things. And it allows you to completely uninstall MS MESSenger.

Explorer.exe is without a doubt the problem. But as I've posted before, I've solved it by not using Windows Explorer anymore.
I use a different file manager that puts Windows Explorer to shame.

31 posted on 03/30/2007 8:02:43 AM PDT by Bloody Sam Roberts (Don't question faith. Don't answer lies.)
[ Post Reply | Private Reply | To 26 | View Replies]

To: Turbopilot; KoRn
I checked the status of Window's messenger as per KoRn's suggestions and found out all are already disabled. Further, I get this note on Local Services, Messenger:

Transmits net send and Alerter service messages between clients and servers. This service is not related to Windows Messenger. If this service is stopped, Alerter messages will not be transmitted. If this service is disabled, any services that explicitly depend on it will fail to start.

I haven't gone through the MS service note yet; that will be next. Also, since everythings locked up, at 99-100% CPU, I don't know how long I'd have to wait to try to reenable the network. After several minutes, I just get frustrated, reboot and enable it after everything comes up. During the day, I can work with the network connections disabled with no major problem. Something at night is using up all my memory. Sounds like my next stop is that MS service note. Thanks for the responses so far.

32 posted on 03/30/2007 9:06:08 AM PDT by CedarDave
[ Post Reply | Private Reply | To 30 | View Replies]

To: Cyropaedia
After listening to the lead tech support for our particular campus talk about all the problems he's had..

Maybe he doesn't know what he's doing.

I personally know a Tech who could get Windows to pop your toast and wipe your butt if you so desired.

He knows his stuff. Dead on..he'd that damned good.

And personally, I've never had a problem with it, either. No virii or BSOD's and I can promise you that I'm pushing my machine to the max.

Most of the folks I've seen on this forum shouldn't be allowed near a computer.

Or a VCR for that matter...

33 posted on 03/30/2007 9:45:31 AM PDT by TomServo ("Jim Henson's Flying Leatherneck Babies!")
[ Post Reply | Private Reply | To 10 | View Replies]

To: CedarDave
It's curious that reenabling the network doesn't quickly return your PC to normal functioning. You can safely ignore the Messenger service that you looked up. While I do recommend disabling that service, it's a completely different function that has nothing to do with MS Messenger or msmsgs.exe except sharing the name "Messenger".

I would check the Microsoft knowledgebase article I posted to you previously and ensure that everything that could run MS Messenger is disabled. If it is, and you're not manually starting the Messenger, msmsgs.exe should never appear in your task manager. Have you scanned your computer for spyware and viruses? Frequently such programs will use file names similar or identical to Windows system programs so that a quick glance at your task manager doesn't show anything out of the ordinary.

You might try going to Start->Search and looking for "msmsgs.exe". The Microsoft program will appear in C:\Program Files\Messenger\, and you may have automatically-created backups in C:\Windows\$[unintelligible directory name]\. If you have a msmsgs.exe file in another directory, it's likely a virus or spyware that copies the Microsoft file name. What if any antivirus/antispyware program(s) do you run?

34 posted on 03/30/2007 9:48:52 AM PDT by Turbopilot (iumop ap!sdn w,I 'aw dlaH)
[ Post Reply | Private Reply | To 32 | View Replies]

To: Turbopilot

The name of the program in Program Files, Messenger is MSMSGSIN.EXE. I disabled it by changing the name to MSMSGSIN.EXE-old.

The other locations are:
msmsgs.exe in C:\I386\MMSSETUP.CAB
msmsgs.exe-0620E8B3.pf in C:\windows\prefetch
msmsgs.exe in C:\windows\ServicePackFiles\i386
msmsgs.exe in C:\windows\$hf_mig$\KB887472\SPQ2FE

The other instructions in the MS service note have me do registry edits which I'll do if everything else fails.

Running Norton A/V, MS Defender, Lava Soft Ad-aware (free copy), Spybot Search and Destroy (free copy).


35 posted on 03/30/2007 11:13:23 AM PDT by CedarDave
[ Post Reply | Private Reply | To 34 | View Replies]

To: CedarDave

Those file locations are all fine, as is your antivirus/antispyware protection. The fact that there's a copy in the C:\Windows\Prefetch directory indicates that the program is running on startup. Renaming the existing copy is a good idea; I'd still recommend going through the Microsoft guide to disabling it so programs aren't trying to access a nonexistent file. You can always check to make sure the program isn't running by Ctrl-Shift-Esc to make sure it's not in your running processes list. Let us know if killing it lets your computer run overnight without a network connection.


36 posted on 03/30/2007 12:12:00 PM PDT by Turbopilot (iumop ap!sdn w,I 'aw dlaH)
[ Post Reply | Private Reply | To 35 | View Replies]

To: TomServo
He knows exactly what he's doing. The problem is with the OS itself. You're being very disingenuous. Too many people are having too many problems with Bill Gates' latest brainchild.

One Freeper told me that they just ordered a new Dell laptop with Vista pre-installed and some brand new Vista compliant software from the same vendor as well. He downloaded the new updates (as advised by Microsoft). He tried to install the new software and the Vista OS wouldn't let him. After spending a couple of hours on the phone with tech support they told that it was one of the new updates that he downloaded that now make his software incompatible with the new OS. They told him if he wanted to install the new software that he would have go into the system itself and uninstall the update himself. That's Vista for you.

The rest of can do a fine job of wiping ourselves and making our own breakfasts thank you very much. Microsoft already has a enough to worry about without trying to take on those responsibilities.

37 posted on 03/30/2007 12:12:27 PM PDT by Cyropaedia ("Virtue cannot separate itself from reality without becoming a principal of evil...".)
[ Post Reply | Private Reply | To 33 | View Replies]

To: Cyropaedia
Yeah - I've seen some of the posts from forum members on computer related threads.

Nearly all of the problems encountered are due to one thing.

We call it ID-10-T..

38 posted on 03/30/2007 1:15:51 PM PDT by TomServo ("Jim Henson's Flying Leatherneck Babies!")
[ Post Reply | Private Reply | To 37 | View Replies]

To: TomServo
Nearly all of the problems encountered are due to one thing.

We call it ID-10-T..

Wrong. The majority of problems are due to the fact that Microsoft rushed out it's new OS before it was ready. Consumers are paying the price. Vista is bloatware pure and simple.

39 posted on 03/31/2007 1:50:20 AM PDT by Cyropaedia ("Virtue cannot separate itself from reality without becoming a principal of evil...".)
[ Post Reply | Private Reply | To 38 | View Replies]

To: Cyropaedia
Wrong. The majority of problems are due to the fact that Microsoft rushed out it's new OS before it was ready. Consumers are paying the price. Vista is bloatware pure and simple.

I'm quite right. The majority of problems are due to the fact that most people can't find their rear end with both hands and a lit match. And Vista runs extremely well. I don't understand how you can address problems for an operating system you don't even use. Which is (again) like most folks around here.

What is it that the rest of us are doing wrong that folks like you are doing so right, anyway? ;-)

I am glad you switched, though. Sounds like you needed to.

40 posted on 03/31/2007 7:54:26 AM PDT by TomServo ("Jim Henson's Flying Leatherneck Babies!")
[ Post Reply | Private Reply | To 39 | View Replies]


Navigation: use the links below to view more comments.
first previous 1-2021-4041-54 next last

Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.

Free Republic
Browse · Search
General/Chat
Topics · Post Article

FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson