backtop


Print E-mail del.icio.us 83 comment(s) - last by overzealot.. on Nov 7 at 12:29 AM


A screenshot of the error.  (Source: ZDNet)
The new Windows Vista still has a significant bug or two

Early adopters of Windows Vista have experienced a rather bumpy ride.  Facing public outcry, Microsoft agreed recently to let OEMs bundle XP with computers as opposed to Vista, a reversal of their previous policy, as reported at DailyTech.

Now a major error in Vista has been found that may affect a number of power users or anyone who, in the words of Microsoft, has "lots of files." Microsofts support pages for Windows Vista feature this jewel, featured on ZDNet.

When you use Windows Vista's Windows Explorer to try to copy files to another Windows computer, the following message may greet you:
"Out of memory
There is not enough memory to complete this operation."
According to Microsoft this can occur if "the files include extended attributes." Or, more humorously, if "you copy lots of files in a single operation."

Ironically users must specially request a hotfix in order to fix this problem which seems like it could frequently occur, as many users do copy "lots of files" between computers on a network.  The problems are due to a memory leak in the Windows OLE component.

The fix was originally planned for inclusion with Vista Service Pack 1 (SP1).  Unfortunately the beta version of SP1 does not contain the fix, so it appears to have been ditched from Vista SP1.

The magic number, it turns out is around 16,400 files.  These do not have to all be copied at once.  If a user copies this many or more files at any time between reboots, the user will frequently get errors. 

"Black screens of death" (BSODs) have also been reported with the error.  Ironically, early reports indicate that the file size does not necessarily matter in whether or not 16,400 files will cause the memory error.

The problem is apparently excaberated by Kapersky Antivirus, which somehow makes the crashes more likely to happen, according to reports.

Windows Vista also has issues with selecting more that 1,500 files.  Doing so will cause dramatic memory spiking and slowdown.  This was another issue that was supposed to be fixed in SP1, but is not currently included in the Beta, so also appears to have been scrapped.

Windows Vista users have many gripes, one of which is the high memory requirements of the system, and overall problems in memory useage and inefficiencies.  Microsoft requires 1 GB of memory to run its OS, but users with less than 2 GB will experience less satisfactory performance.

As Microsoft struggles with its Vista woes, it can take solace that users will likely simply go back to its other product -- Windows XP.

Update 10/17/2007:

As some posters noted, it is important to differentiate that this only occurs when you copy files from one computer to another.  This is a typical scenario in a business or home network setting, so it is still significant to many users. 

Again, this is not fixed in the Service Pack 1 beta, though a hot fix is available upon request.  Note the crash does not occur during every copy, but does occur more frequently when running Kapersky, as noted.  This article only intends to point out a current flaw in the Vista OS and not to discount Windows Vista or Microsoft's overall efforts to produce quality software products.  Microsoft has indicated its intention to fix this error, and will likely include the hotfix in a future service pack, possible SP2, though this may be some time in the future.


Comments     Threshold


This article is over a month old, voting and posting comments is disabled

Not just copy
By Murst on 10/17/2007 12:03:20 PM , Rating: 3
There are lots of issues in vista, from copy (as this article covered) to other basic stuff like delete.

For example, open up command prompt and navigate to a directory on your file system (make sure it has other directories/files in it). Now, open explorer, and navigate to the same directory that you have in the command prompt.

Now, shift+del the folder in explorer. You'll get an error saying "Could not find this item. This is no longer located in <location>. Verify the item's location and try again." If you close the command prompt, the error goes away.

Stuff like this is just annoying in Vista right now.




RE: Not just copy
By Master Kenobi (blog) on 10/17/2007 12:06:58 PM , Rating: 2
*Tested*

I was able to delete just fine, no error.

Any more details about this bug, maybe I did something differently?


RE: Not just copy
By Murst on 10/17/2007 12:10:13 PM , Rating: 2
Strange, I've done this on two different computers at work.

You sure you have the directory open in command prompt, and then you've attempted to delete the directory in explorer?

Like, go to c:\test in command, and try to delete c:\test in explorer. On both versions of Vista Business at work, using Shift+Delete causes this error.


RE: Not just copy
By TomZ on 10/17/2007 12:16:10 PM , Rating: 2
I get an error "Folder In Use" which is correct. That's on a fully-updated Vista Ultimate, and also on a different machine with Vista SP1 Beta.


RE: Not just copy
By Murst on 10/17/2007 12:17:40 PM , Rating: 2
You're not holding "Shift" when you delete. If you hold down "shift" and press the "del" key, you do not get the error "folder in use".


RE: Not just copy
By Murst on 10/17/2007 12:19:22 PM , Rating: 2
fyi:
shift + del = permanent delete (no recycle bin)


RE: Not just copy
By TomZ on 10/17/2007 12:21:49 PM , Rating: 2
Uh, yes I do, regardless if I use shift or not.


RE: Not just copy
By Murst on 10/17/2007 12:24:54 PM , Rating: 2
Hmm... maybe its something to do w/ our policies on the network then. Its definetally a bug here though (easy to fix, but still annoying).


RE: Not just copy
By Master Kenobi (blog) on 10/17/2007 12:35:58 PM , Rating: 2
I'm on Vista Ultimate 64, Workgroup not Domain. It may very well be something with Domain Policies.


RE: Not just copy
By TomZ on 10/17/2007 12:46:32 PM , Rating: 2
We have a domain here, so it's got to be more than that.


RE: Not just copy
By JasonMick (blog) on 10/17/2007 2:05:54 PM , Rating: 4
Alright,
I know you guys gave me some flak for this blog. I am sorry I did not clarify that the transfer was between computers.

I know that Windows Server 2003 is a valid business solution, but many businesses are switching to Vista, so this bug could be a problem.

It may not happen that often. However, what follows are severe consequences including menu and tab disappearance, reboots, and black screens of death, which appear to be solely linked to and triggered by the memory leak.

A lot of programs have memory leaks, but Windows is typically better than most and typically held to a slightly higher standard because of this, and because it operates on an OS level as opposed to a traditional leaker like Firefox.

Besides..its just an article, pointing out a bug found. If you love Windows so much that you can't bear to read about bugs found in it, don't read it. If you have constructive criticism or observations terrific. But please don't simply discredit the article since you disagree with it, as I am trying to present an issue that may be important to some users and may result in frustration and inconvenience. If these users premptively request the hotfix, they can save themselves potential hassles or better yet, motivate Microsoft to include the fix in SP1.

I would also like to note that even though this article is a blog, it is less editorial and negative towards Vista than some headline articles such as the XP OEM article I linked. Overall I feel that Vista is relatively solid and is certainly headed in the right direction. However, when there is a problem, it should be noted, I also feel.

Thanks for your time.


RE: Not just copy
By TomZ on 10/17/07, Rating: -1
RE: Not just copy
By JasonMick (blog) on 10/17/2007 2:14:32 PM , Rating: 4
Again I feel the blog points out a legitimate problem.

Obviously the article is factually accurate, esp. after I clarified the exact situation that bug occurs in.

As to the slant, like I said in the update note, I personally think Vista is headed in the right direction.

If anything, coverage like this motivates them to include the fix in the next SP and avoid worse publicity when someone makes a stink about lost data.

I will try to publish something good about M-Soft in the near future to even the cosmic balance.


RE: Not just copy
By TomZ on 10/17/07, Rating: -1
RE: Not just copy
By porkpie on 10/17/07, Rating: -1
RE: Not just copy
By Oregonian2 on 10/18/2007 2:11:22 PM , Rating: 4
Sounds like it's probably not a problem except for those who do silly things like backing up directories or disks to a networked fileserver. Just don't do backups and one is fine!

I'll do that manually sometimes, esp. when replacing a disk.

Ick, glad I've XP.


RE: Not just copy
By TomZ on 10/18/07, Rating: -1
RE: Not just copy
By aos007 on 10/18/2007 6:29:55 PM , Rating: 4
Exactly HOW would they reach a wrong conclusion????? This is exactly the kind of news I like to hear as it will help my decision about when to switch to Vista - if ever.

I copy huge number of files on my HOME network on a REGULAR basis. E.g. music files or photos or various PDF datasheets or simply backup/restore from one machine to another after I reinstall windows, linux or whatever because I like to fiddle with hardware and buy new motherboards/CPUs often. First, Vista had a problem with slow network copying. Now it has a problem with large number of files. These are NOT minor problems AT ALL. Copying files is a BASIC feature of an OS.

Especially if you read the article: while the number of files required to trigger bug seems high at over 16 thousand, the effect is CUMULATIVE as long as you don't reboot! Even if you dismiss a single operation taking 16000 files, it's not a stretch to get there if you keep your machine up for a while.

Besides, if you're actually doing any work you can easily have project folders with thousands if not tens of thousands of files (source code, object code, libraries, HTML documentation, log files, test run results etc.)- if you're a programmer as you claim to be you should know that. And I haven't seen any indication that the machine you're copying to or from needs to be Vista - where's Windows 2003 even coming into play here?