NTFS file system glitch
I’ve been using NTFS for almost a year now and I’ve like its stability and low maintenance. NTFS doesn’t fragment as much and allows for greater disk security. However, ever since I installed Windows XP, I’ve gotten a cryptic error when running chkdsk.exe from the command line. I talked to Microsoft and one of their tech support agents replied back today. Read on to see how the conversation went.
My initial post
Problem Description: I’ve been running Windows XP Home for almost a year now. I have been using it with my other computer, a Dell Dimension 8100. The problem started with that machine but I have seen it now manifest on this one as well. Originally that system ran Windows ME (Dell installed) and then I upgraded it to XP Home using the XP upgrade CD. I converted the file systems on that machine to NTFS via the command prompt. I have three hard drives on that machine, two of which are EIDE and the third is firewire.
I noticed that somehow a glitch happened in my NTFS file system on that machine. I started getting messages identical to the attached file, chkdsk.txt. I would run chkdsk while logged on and it would say that there is an error with my volume bitmap. However, this error only appears when checking C:, not the other two hard drives.
When I went to upgrade this computer, I backed up all of the files across my HPNA (homeclick homeconnect) home network to my firewire drive on the Dimension 8100. I then clean installed Windows XP Home on this machine using a store bought boxed upgrade edition of XP. I did a long NTFS format of the primary drive. I installed all of my essential programs and ran a disk check via the command prompt. The error had not manifested.
However, the minute I copied files from my firewire drive on the other computer, chkdsk reported volume bitmap errors on my freshly installed copy of XP on this machine. This leads me to believe that there is some sort of “glitch” or error in my documents that messes up the NTFS file system.
The documents are primarily graphics (GIF, JPG), Word documents, or MP3s. I had recently run a virus scan and nothing came up.
CHKDSK recommends to run a check with the /F switch, and I did that. Windows just doesn’t repair the error. I don’t know if there is anything wrong with CHKDSK, but this error has now appeared on three of my computers, including one that was running Windows 2000.
I was wondering if there is any way to resolve this error. I am willing to format to FAT32 to get rid of the problem, but three of the hard drives I own are over 32GB and Windows XP will not format them to FAT32.
Any ideas? Thanks.
Microsoft’s reassuring answer
As I understand, the issue is: You received the following error report when performing chkdsk.exe tool on your Windows XP:
Security descriptor verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
If I have misunderstood your concerns please let me know.
According to my research, I have included the following information for your reference:
This problem occurs because when Chkdsk is run against an NTFS volume, chkdsk.exe may report that security descriptors are in the database that are no longer referenced by any file or folder, and that it is removing them. However, Chkdsk.exe just reclaims the unused security descriptors as a housekeeping activity, and is not actually fixing any kind of problem.
Microsoft has confirmed that this is a problem in Windows. Fortunately, this error message is an informational message, and can be safely ignored.
All NTFS volumes contain a security descriptor database. This database is populated with security identifiers that represent unique permission settings applied to files and folders. When files or folders have unique NTFS permissions applied, NTFS stores a unique security descriptor once on the volume, and also stores a pointer to the security descriptor on any file or folder that references it.
If files or folders no longer use that unique security descriptor, NTFS does not remove the unique security descriptor from the database, but instead, keeps it cached. Like any caching strategy, you want to keep the cached information as long as possible because it may be used again.
To determine if more serious problems exist before scheduling or running chkdsk.exe with the /f switch, run chkntfs <drive letter>:. If this command reports that dirty bit is set, there may be real damage that needs to be fixed.
137 comments
(5 years, 8 months ago)
Well….This is quite annoying….Does anyone know if there is a fix coming? It seems to wreak havoc with the speed of my drive, not to mention clicking that emanates (if I take the drive and make it the non-boot drive, there’s no problems)….What’s Microsoft’s problem? FIX IT !!! :)
(5 years, 7 months ago)
If your problem is that WinXP will not format FAT32, then you can just use a win98 boot disk, with the format command. as far as i can tell, the win98 boot disk is one of the best pieces of software microsoft ever wrote. works every time.
(5 years, 6 months ago)
I as well am seeing the same conditions as noted above. I also received the same information from MS Support. It even looks to be a cut and paste job. So I am assuming we are not alone and MS has a carbon copy answer for everyone.
I believe my situation occured because of a recent MP3 player purchase the transfer of MP3s to the player via USB 2.0. I had not seen the error before the MP3 Player purchase.
I am being told to ignore the error (which Norton System Works 2003 Pro Disk Doctor also detects). I wish an answer or patch would come sooner than later.
(5 years, 5 months ago)
On my computer the only way I could get rid of the glitch was to do a low level format on the drive. Be sure to check the warranty on your drive since this technique may void it. I know the big manufacturers like IBM, Maxtor, and Western Digital have programs to do a low level format on their web sites. See if you can find one and try that before reinstalling. Note that some of the low level format programs require a previous version of Windows to format them because they are outdated. Usually you can prepare a low level format boot disk from Windows XP fine though. Good luck!
(5 years, 5 months ago)
I’ve been getting this exact message when running CHKDSK on my C: drive. First off, some programs refused to open, fault errors came up in mirc, cuteftp pro, etc. and the interface on Paintshop pro and LiveUpdate went a bit f**ked as well as some other applications. Start Menu appeared weirdly, then my right mouse button sometimes stops working. So I ran chkdsk, it found the Volume Bitmap error, so I rebooted to fix it.
Upon bootup, nothing at all would start, not msn messenger, not IE and about 30 services failed to load. So I rebooted again and all’s ok.
I ran virus checks and HDD tests, one error came out of the HDD test and it suggested to low level format. I decided not to go any further since I didn’t have time to waste so I swapped the Hard drives with a spare one I had. But again, all these problems noted above started happening again!
It might be Windows XP, since I restored a backup image of my winxp installation with a couple of applications that were originally installed on my previous hard drive. Still not sure what’s going on, been tearing my hair out for a whole week. :-(
Gonna try a full proper format and start afresh.
(5 years, 5 months ago)
Hello all!
I don’t know if I can explain this in English.
So my problem is: When I schedule the CHKDSK to check the C: volume, It start after boot and says: “This is not an XP volume Continue? Y/N” And immiadtely answers no, and goes on. My Xp is good in spite of that, but my User profile did not load, and had to make an other one, and copied the old user files there, its working.
But!
In XP i run CHKDSK: It mentions some errors and crosslinked files and lost chains. And suggest that I try CHKDSK /F, but in XP “The volume C: cannot be locked”. So When I go in Recovery console, and check the C: volume with /F, i get something like this “There were one or more errors could not be corrected”. (This is not the exact message)
What can I do? Can I correct this?
(5 years, 5 months ago)
Sorry, I forgot to mention, that the drive is FAT32 not NTFS.
(5 years, 5 months ago)
I was having the cross-link file and lost chain errors just 2 days ago. I had just installed ALL of my program on the drive so I was naturally quite ****ed because when chkdsk fixed the errors, xp would load but my profile and many programs were missing files and serious screwed. I reformated to ntfs and now I get this security descriptor error when I run Norton Disk Doctor 2003, but everything has been working perfect for the past 2 days. Since you are using fat32, what would the size of your drive be? The FAT32 file system has around a 32 gig limit, and to the best of my knowledge, that was my problem. I have a 40 gig drive.
Now my question is this; is this a NTFS glitch or a hard drive delimma that requires a low-level format? I do not want to have to go through the format and reinstall process for a 4th time, especially if no one’s 100% sure it’ll fix it. Will this cause any other problems in the near or distant future? I ran the chkntfs that that e-mail suggests and it says the drive is clean.
(5 years, 4 months ago)
When I run a CHKDSK XP Home tells me that it needs exclusive access to my disk and can schedule this for a reboot. When it reboots it will run a full check, but when it finishes it hangs and I need to manually shut down the computer. This, of course, prompts a restart of the CHKDSK upon reboot at the end of which it will tell me once again that my disk is fine…and freeze. If I run Norton Disk Doctor without “Fix Errors” checked it shows me that my Security Identifiers are bad and to run with “Fix Errors” checked. If I do this…XP takes over on reboot and the problem starts over again. Only way out; Manual Reboot and Invoke Last Known Good Configuration. Any Suggestions??!! PS, Have tried Repair Console CHKDSK /r…no avail
(5 years, 4 months ago)
Yes this doesn’t sound good at all. If your computer is freezing up after running CHKDSK, there may be something wrong with the Windows installation or the hard drive itself. If the repair console didn’t work, I suggest reinstalling Windows and maybe even low-level formatting your hard drive just to be safe. Be sure to contact Microsoft prior to reinstalling just so you don’t have to burn a couple of hours reinstalling when there’s a quick fix.
(5 years, 3 months ago)
This error cause partition magic version 8.0 not to work correctly i want to split my HD up without losing my data but partition magic reports error 1513. the solution is to run chkdsk as the powerquest website say i do this and still the problem occurs.
(5 years, 2 months ago)
Thasks to all who posted here on Windwos XP SP1, Norton DiskDoctor 2003 and problems with found errors ‘Security Descriptors’. I’m encouraged that the problem is probably software and I’ll back-up more and proceed with caution.
Thanks again… Ron Ellis
(5 years, 2 months ago)
Sign me up :-) same Norton wincdoc arrors, same descriptor errors, but I’m lucky I guess I only get 4 unused index entries at the most. Had a friend just run CHKDSK and then had her look at application logs. 133 unused index entries :/, As for the guy who’s machine locks up after scandisk, I have 2 machines an each one have always done it. One has XP Pro and the other 98SE. The mouse freezes up an you need to reboot using the KB, to return to normal. Windows = untidy housekeeper (( fire em ))
(5 years, 2 months ago)
I came across a sidenote somehwere and is currently trying to re-locate that website. It said something about disabling some cache setting from within BIOS. There may be a timing issue with the BIOS cache settings and how NTFS cleans itself up when Windows is shut down. I have experienced this problem over and over again (since Windows XP came on the market). I have tried every suggestion posted everywhere on the web to no avail. This has became a personal vendetta. It is even more frustrating when the errors pop up after a clean install. You can imagine how upset I was when I thought it was a hard drive problem, which resulted in me buying a new hard drive - an unnecessary purchase since the problems came right back on the FIRST install. The cache tip sounds legitimate. If someone else can help me determine if this solves all of our problems, we may have a found a solution that I will be ****ed surprise that even the techies at Microsoft never thought about!!!
(5 years, 2 months ago)
I have experienced the Norton File descriptor errors and the CHKDSK C errors — none of which are of any significance — simply software false positives. On one pc I found that Partitioning and placing all data in My Documents in a new partition resolved the problem — no error messages from CHKDSK or from Norton.
(5 years, 2 months ago)
The Norton File Descriptor errors are a big significance because you cannot use the Norton Speeddisk utility unless it’s fixed.
(5 years, 1 month ago)
Great post on an obscure problem. I was getting really concerned. I’m glad its not as big a deal as I expected.
(5 years ago)
Hi I’m another victim of this “glitch”. I purchased a Maxtor 160GB drive and installed this into an old P3 (500MHz) system, XP Pro. Another 40GB Maxtor drive had been fine for years but with this one (partitioned into 3 equal parts) the dreaded chkdsk error. I have run powermax and the disk is fine. I have already formatted and clean re-installed so would rather not do this again and hjave avoided low level format … so far. I have upgraded the BIOS, put a RAID PCI card in (new IDE chipset) - thought it might help, used the Maxtor large drive utility but still getting chkdsk errors that are temporarily sorted by chkdsk /f but reappear quickly. Does anyone have a final solution for this? Is a low level format the cure…:(
(5 years ago)
Sorry forgot… is it really not serious? My system previously has become unstable and crashed requiring the original re-install. The memory is ok, it is not overheating, the drive is ok hence I concluded it was due to this chkdsk error. I run the chkdsk /f with every boot now but when I haven’t re-booted for a while the system is still showing signs of instability.
(5 years ago)
Yeah I’d go with the low level format. I have a Maxtor drive and that fixed the CHKDSK error for me.
(5 years ago)
I am having the same problems on a XP Prof machine. I get the “Fixing errors in the Volume Bitmap” message whenever I run chkdsk. This is a machine with one 76Gb partition on a SCSI RAID10 subsystem.
I tried doubling the log file size with “chkdsk /L:….” but that didn’t help either.
No matter what I do - the volume bitmap error just keeps showing up. This is really annoying and makes we wonder what I paid money for. I’m having so many software problems these days that I am starting to realize why people switch to Linux. Not that it works any better - but at least you don’t have to pay for it.
Maybe I’ll downgrade to Win2k Prof …
(5 years ago)
Downgrading won’t fix the problem. I’ve seen the message on 2K as well. The only way I know of to get rid of the glitch is to low-level format.
(5 years ago)
I’ve just put an additional larger hard drive in my XP system & attempted to copy the old C: partition onto the new drive. I’ve tried this with both Powerquest Partition Magic 8 & Powerquest Drive Image 5 but both give up after a short time with Error 1513 Bad attribute position.
Through windows, Norton tells me I have problems with the dreaded “Security Descriptors” but when I reboot for chkdsk /f no errors show up. I�m now stuck & can neither copy nor image my C: partition.
My system seems otherwise OK & about as stable as can be expected from a MS product, but that is not much consolation when windows prevents me from backing up my data!!!
(4 years, 11 months ago)
Ok… I have re-installed a 40GB Western Dig drive that was working fine for years prior to the upgrade to the 160GB drive. Full format, clean install XP Pro, files and settings transferred and … same error again.
The 160 GB drive is now fine with no error. I have tried an earlier recomendation and moved My Documents to another drive… no improvement.
I didn’t have this problem before and used XP Pro so any ideas? I have recently started using XVID/DIVX (largish files 1GB) and also windows movie maker… some 10GB files. Might it be a setting in windows… the files and settings transfer wizard might have carried it across…
I didn’t bother with the low level format as I had a new drive but the problems seems to be windows and not the drive.
Anyone any ideas?
Thanks
(4 years, 11 months ago)
I’d try the low-level format. I couldn’t get rid of the problem without doing it. I’m sure it was a glitch in Windows but this is the only way I know how to correct it. Make sure you’re using a legit copy of Win XP and install all the patches, especially SP1.
(4 years, 11 months ago)
Interesting thread. I am seeing the same problems.. I get some strange boot problems on two different computers running xp home. One gets halfway through booting windows, stops, and reboots. It usually works the second time. The other occasionally just hangs halfway through boot. Reset and it boots.My problems started when I charged permissions for file sharing on my home network. That messed up Norton protected recycle bin. There are postings on symantic site about this. I cleaned and disabled Norton Protected Recycle and things worked again. I just turned off Norton automatic update, and now I am getting Norton reporting security descriptor errors (on NTFS) but CHKDSK finds nothing wrong. I wonder if the problem might be Norton. Anyone with these problems NOT using Norton? Anyone with problems NOT using XP network folder sharing on a home network? This is frustrating.
(4 years, 11 months ago)
I’m guessing that it is Norton. I’ve never heard of this happening but remember that Norton Utilities (included in SystemWorks) was written a long time ago, and yes it works in XP, but it isn’t designed for XP. It’s very possible that it corrupted your partition.
(4 years, 10 months ago)
I am still getting occasional errors and yes I am using Norton System Works 2003… good one I’ll try it!
(Can’t be bothered with the low level format and re-install yet…)
(4 years, 10 months ago)
An yes I am running a home network with folder sharing…
(4 years, 10 months ago)
I have the same glitch as well. If you read Microsoft’s answer and can understand what it is saying you would know that this is totaly insignificant unless you are bothered so much by seeing the message in chkdsk. There is absolutely no serious problem. It is just security identifier space that is being kept in the file system. If you were at some point to write over all those entries the problem would go away. But it is not really a problem since it does not waste space or cause corruption. Yes a low level format would fix it because the disk is rewriten with 0s all over (to explain it as simply as I can) so the security descriptor space is overwritten as well but there is absolutely no reason to get in the hassle to do that just to avoid a silly message in chkdsk. A normal format won’t fix it as it overwrites just the MFT. If you have other problems like software crashing or not starting up as a I saw in some posts they are totaly unrelated to this. Search for the cause of your problems elsewhere.
Sorry for any bad use of english it is not my native language:) I’m Greek.
(4 years, 10 months ago)
Well that’s good to know. When I had the problem, Microsoft hadn’t written anything about the problem, so I figured it was serious. I’m glad to see it’s just a minor glitch.
(4 years, 10 months ago)
i am experiencing some of the same behavior in my XP system… but my problem is Diskeeper 7.0 not wanting to run scheduled defrags on my system (C:) drive. When Diskeeper cranks up to do a scheduled defrag I get an error message to this effect “Diskeeper cancelled defrag due to inconsistencies on the disk, please run CHKDSK”. This is not the exact message but if you have seen this message you know what I’m talking about. Now the real puzzler is that to get Diskeeper to run, I can reschedule the defrag to run immediately(right now, right after i get the error message) and it will run the NEW scheduled defrag without me having to run CHKDSK or any other corrective software before hand. So why does Diskeeper see inconsistencies on the first attempt, but then crank right up on the second? This seems to only be a problem with the auto-scheduling, but that’s why I like Diskeeper!!! I don’t have to worry about defraging and my system stays as frag free as possible. This is very annoying and it seems to all fall back on the NTFS unused security descriptors error / volume bitmap error.
(4 years, 10 months ago)
Minor glitch? If you have an error on your primary drive and you are trying to use Partition Magic, like I am trying, because of my 2 GB c-partition is too little for XP which is growing in size all the time. Now it 1.6 GB!!!
So, if there is an error, you cant resize your partitions. XP and NTFS is so ****ed up! I want some refund! I bought XP for 140 euros and it sucks. IT SUCKS! I never buy original MS-product again. I get constantly messages saying “There is not enough free space on drive C, try to free some more” but I cant, because XP eats all and can’t use software like partition magic. :)
I have spend my expensive time so far 58 hours to solve this issue, my tax is 20 euros / hour. Please pay my bill, MS. :D And fix your ****ING software, or I will shoot somebody. Bill Gates propably. :D
(4 years, 8 months ago)
The reason I’m here is becasue I lost my system partition in win2k server. I was looking for optimized speed with diskeeper. Get a stop error(inaccessible boot partiion, I smiled… honestly) Running off a rescue partion right now. Having some extra drives is nice in any case. Lost my data twice with partiton magic over the years, once with diskeeper today. Got two maxtor 40s on raid 0 for boot 80Gb baracuda and maxtor 200GB for data. I use part of each of the extra drives for mirror set for critical data. I will lose nothing to very little for data, time though time….(I use ghost too, but…never mind) No matter how bad your filesystem pukes you can almost always get your data back with “getdataback” an excellent recovery software when you give up trying to “fix” the problem. extra drives are handy to copy the data on to.
[removed]. I may be finding out what getdataback thinks about raid real soon.(4 years, 8 months ago)
I have same issue on 3 machines, 2 are a ghost(Norton) of the first. I’m at a loss as I’ve never this kinda problem before. All 3 machines were working, but now chkdsk runs everytime the machine boots, finding a bootex.log file and deletes it, then fails to fix the problem or reboot. If skip the test the system works fine. CHKDSK says the filesystem is dirty, but it’s a clean installation!
(4 years, 7 months ago)
I have similar prob-xp on a dell laptop partitioned drive with pm 7, now can’t put it back
norton continually says either security descriptors or indices not fixed-one right after the other!
pm shows error 1513 and stops
multiple runs of chkdsk /f do nothing
I have unallocated spoace on my drive that I can’t recapture my 30 gig disk is 18g-trouble running diskkeeper since not enough free space
(4 years, 7 months ago)
I had this problem. Heres How I fixed it. Get hold of a copy of PQ PM, any version from 5.0 up. Insert the CD into your drive. Don’t install it but create the rescue floppy’s. Boot from these and convert all your drives to fat 32. Shut down and reboot into windows. Go to Start/Run type cmd hit return, from the command prompt convert your drives to NTFS using the “nosecurity” switch i.e. to convert drive “C” type “convert C:/FS:NTFS/nosecurity” without the qoutes,and leave a space between convert and C: this will rebuild your MFT and reset you security levels to default. Follow the onscreen instructions re scheduling the convert at the next reboot. Once the conversion is complete run NDD and you will see all is well. This worked for me, I hope it helps you, and it leaves all data intact without the need for a low level format.
(4 years, 7 months ago)
For those who got some problems with error 1513…look at this…
there’s a fix but i cant find it on the web…anyone got it?!?! if yes post the link plz !!!
(4 years, 7 months ago)
Well gang,
Just wanted to post my experience with this Volume Bitmap problem.
First I began to see it on my external hard drive connected to my USB 2.0 port. It ran perfectly for a while and then after what I think may be a stalled system requiring a Power Off button push to resolve (don’t you just hate those failures?). After the machine rebooted (WinXP Pro on ThinkPad A31p system) I noticed that when I manually chksdsk’d the external drive that I would get the error message everyone is seeing. The problem actually got worse because at one point the system would schedule a chkdsk on the drive EVERY TIME. Man, was this frustrating.
Anyway, I complained to the external drive provider (Apricorn, but Fujitsu made the drive), they sent me a new circuit board adapter (it attaches to the drive’s connector and translates the r/w to USB) and suggested to exchange the old for the new. Did this but kept getting the error message even though the chkdsk on every reboot went away.
Called Apricorn and the tech rep said to stop/disconnect the drive just before the next shutdown. Once I performed this, the drive began to behave properly. Don’t ask me why, but that is what solved my problem and I no longer see it at all.
Hope this helps someone.
Charles
(4 years, 7 months ago)
I was able to fix this on my PC using these steps:
Open ‘My Computer’
Right click any hard drive or other device
Choose ‘Properties’
Select the ‘Hardware’ tab
Either double click the hard drive in question or
Single click the hard drive to select it and click the ‘Properties’ button
Go to the ‘Policies’ tab
Uncheck ‘Enable write caching on the disk’
There is also the note: “This setting enables write caching to improve disk performance but a power outage or equipment failure might result in data loss or corruption.”
Run chkdsk now without the /f parameter and you should not see the errors
You can reset this setting and verify that the ‘errors’ reappear.
(4 years, 7 months ago)
That seemed to fix the problem initially but the ‘errors’ returned.
I noticed that chkdsk reports differently when run several times consecutively. Strange that sometimes I receive the errors and sometimes nothing.
(4 years, 7 months ago)
i get this problem on two new machines I built for our kids :( this error is really annoying and the two machines are connected to server 2003 standard and every so often when I try logging in to an account (domain) it says the account is corrupt, **** microsoft :(
I was running Norton Internet Security Professional which was so unstable I s****ped it and got a refund.
not sure wether to reboot, please email me @ tmancey@tiscali.co.uk or msn me if you have ideas.
thanks
(4 years, 7 months ago)
I’m experiencing the same problem (14JAN2004) with my new HP Pavilion zt3010us (zt3000 series) laptop. It’s got a 60GB hard drive shipped as formatted with NTFS.
Since there seems to be no fix for this problem, I’m going to lean toward conspiracy theory and assume that this is an intentional glitch… an attempt to prevent me from resizing the Windows partition and installing an alternative operating system for dual boot.
(4 years, 7 months ago)
I’m getting a similar error in WinXP Pro.
I’ve got 2 hard drives:
The second drive, when running CHKDSK D: /F /V /R /X gives the following error: “Windows replaced bad clusters in file 809 of name \backup\weekly.bkf”
It gives this error no matter how many times I run CHKDSK, but if I delete weekly.bkf (a 4.5GB file), it says there are no errors on the drive!
It does this if I run it within WinXP, or if I boot to Safe Mode Command Prompt and run it there.
I’ve got write caching disabled on both drives, and I’ve gone into the BIOS and disabled Burst Mode. The D: drive was a FAT32 drive that I converted to NTFS.
Any ideas on how to prevent geting this error on large files?
(4 years, 7 months ago)
Got it! I figured it out! It’s the WinXP hard drive compression that’s causing the data errors.
I’ve noticed that it only happens (on my computers and on others’ computers whom I’ve conversed with) when there are files over approximately 4GB in size.
I disabled WinXP’s hard drive compression, and ran CHKDSK. It fixed a couple of security descriptors. Then I ran it again, and it sailed through without any problem. No bad clusters, no security descriptor problems, etc.
Even after rebooting a few times and heavily using (copying to and from, saving to) the hard drive, no problems.
(4 years, 7 months ago)
Oh, and I also disabled write caching on the hard drives. I haven’t really noticed a performance hit.
(4 years, 6 months ago)
No, it’s not any hardware issue. I have no compression enabled and still have this *ing problem. The reason for all this is that Windows is a really wonderfull piece of **. WE ALL SHOULD START USING LINUX AS A SECOND SYSTEM, FORCING COMPANIES TO DEVELOP FOR THIS OS. Even MacOs now is unix and we are stuck with this big piece of *** called windows.
There’s an utility on linux, something free called “wine” that claims to run any winblows software on linux… I am thinking on try this to see if it works…
Let’s all move to linux!
(4 years, 6 months ago)
I’m getting the Security Descriptors error in both Windows Scandisk and Norton Windoctor. It occurs for me on my C and D drives but not my E drive (RAID PCI). Also, no change with Write Behind Caching on or off. However the Write Behind Caching is not available on my E drive which as I said is not having a problem.
(4 years, 6 months ago)
I am getting a diffrent problem with CHKDSK running itself everytime I start windows XP, then it mention recovering lost files, correcting error with $I30 file 8949, anyone else getting this problem?, any ideas?..thanks
(4 years, 6 months ago)
OK I have a not entirely related problem.
I am running a RAID 0 (2xMaxtor 60Gb) under Xp home and just tried to add a 120 gb seagate.
No matter what, I always wind up with the same problem: Once the XP GUI starts, at the time the login screen comes up I begin getting messages similar to this: “$MFT C/..” cannot be saved..” Basically the MFT data for all of my partitions cannot be saved.
Boot info: The new HDD gets detected first and is defined as HDD-0 (1st HDD) Then the raid array is initialised (detected as second HDD)
It is as though the seagate drive is insiting on taking the c: position.
Nothing I have done has fixed this problem.
I want to run xp from my raid array.
I have installed windows on the c: partition with the new seagate ide as D: I have defined my first raid partition as d: installed windows there and defined the seagate ide as C: etc etc… I have tried primary partition, logical partitions, scanning the disk… Boot settings in the bios…
Nothing works.
Sooner or later the problem crops up again.
Without the new ide HDD my system has been extremely stable.
On my last install I had the new seagate IDE as c:, my first raid parition as D: , installed windows there and set bios to boot from HDD-0 (the ide drive with the c: partition where windows was definitely not installed) ..even though boot other devices was disabled, it ran fine for several hours and numerous reboots before the mft problem began yet again. BTW: When I set my pc to boot from the raid array I got the message BOOT DISK FAILURE.
Very wierd.
I have spent more time watching chkdsk scroll up and down my monitor than most people ever spend sleeping.
I know its not entirely related, but I have a feeling this might be a NTFS issue.
For my next trick I will install windows on a FAT32 partition and see how long it takes to die horribly.
(4 years, 6 months ago)
I keep getting, One of your disks needs to be checked for consistancy. Started when I installed a SATA WD 70 GiG with New Install of XP. Any Suggestions?
(4 years, 6 months ago)
Hi All! My computer have four partition. But after i reinstall systemm, my system is broken. I can’t see all partition in my system. Please help.
(4 years, 6 months ago)
Well, You’ll find no solution in my post but maybe my info will help someone narrow down the issue.
I don’t have drive compression enabled but I do have the Win XP NTFS chkdsk problem that doesn’t seem to go away. I have a WD JB1200 HDD with 4 partitions. The problem is on my G partition which is also my system partition. There are no files larger than 500MB. I do not use Norton system utilities but I do use Nortons Antivirus 2004 which installs Nortons Protected Recycle Bin. A game I have installed on the G drive, suddenly started locking up upon it’s starting which I believe is quite possibly caused by file corruption.
(4 years, 5 months ago)
Hey guys, just finished reading through all the posts here, thought maybe one of you tech’s out there know a solution for this one I got yesterday when I installed WinXP (first time) after I got tired of Win2k’s small&funny behaviour problems.
I have 2 drives, the booter is a 6.5 GB Quantum Fireball (ancient but it still works fine) and the other is a Western Digital 250 GB with 8 MB, caviar series, bought some months ago and has performed well on Win2k & Win98se. Mainboard is an ASUS (cant remember the model atm) and there’s 512 MB RAM (3 chips) on it.
The FB is my bootdrive, 2 partitions. One NTFS (boot-partition) and one FAT32. The WD is storage, NTFS as well.
I only have problems with the WD, not the FB.
Here’s the problem, after I installed WinXP the last 20 GB’s of music I downloaded (before WinXP) disappeared from the disk. Only the music, not the movies or apps at this stage. The space were still occupied though, so they weren’t properly deleted they just didn’t show up anywhere.
I ran chkdsk /f and booted and got a TON of “Index error $I30 in file ‘xxxxx’”, then it went to work fixing everything. Jolly good I thought… Guess I’m an optimist sic
Suddenly around 20 GB of space were availible, hmmm… Nice fixing! argh
The rest of the music downloaded when I still had Win2k ‘worked’, in the manner that I could still play some of the files but they had been mixed with other files so starting Moby would be Moby for maybe a minute, then suddenly the middle of the song would be Bill Hicks, then back to Moby towards the end.
Tried to install Winamp to rule out that it was a MediaPlayer bug(there I go with the optimist thing again, meh), but then the installer I had lying around wouldn’t run. Deleting the installer and downloading it again worked fine.
This tells me its gotta be a file-system glitch, but I’ve scoured the net for a few hours now and I haven’t found anything that even resembles a solution, or a description of the problem so someone, anyone, who knows how I can fix this without low-levelling my drive (strangely I don’t feel like collecting 200+ GB of hard-to-find movies etc again…) please tell me, this is getting annoying.
/Kel
(4 years, 5 months ago)
same problems here :(
read this please, I found it interesting:
there was nothing working for me… except low level formating the drive… wich I don’t want to do… :(( so I’m thinking to make an asm program wich manually unset the dirty bit… but keep in mind that the errors are still there…
until then… I’m using this trick to escape from the autochek loop:
where “gh” are G: and H: labels of the partitions I don’t want to be checked at boot time…
(4 years, 5 months ago)
Look, I have been working with drives for 5 years now…
Native Windows disk uitilities can be awkward and potentially painful.
The best way is to get your hands on 3rd party utils. The ones I have found good are:
Without the surface testing option crossed…formatting with Paragon took a second….
Very good solutions…without the hassles and time wasting…staying up till 3am in the morning is a waste of time, esp if you have someone in bed waiting for you!
Rohan
(4 years, 5 months ago)
I just read the entire thread…WOW! Now I really don’t know what to do. As some of you have been talking about, I have a problem with the Security Descriptors (using windows xp home). Norton Disc Doctor says there are problems and said I must schedule a repair when i restart. I do this, but, when I restart Checkdisc loads instead of Norton. It reports that everyting is fixed but when I run Norton again, the problems are there. If I run Disc doctor multiple times consecutively, it reports errors once out of 3 times. I recently built this computer and if I am going to need to reformat the drive, I should do it now before I have a lot of things on here. However, I don’t want to reformat if there is another way. What does everyone think? Also, what caused these errors to begin with? If I reformat and start over, wouldn’t the same problems be there again if I do all the same things I already did? If so, why would I want to bother? I have been unable to create a backup of my hard drive too. Using Norton Ghost and a CD burner (MSI 52x). It gets part way through and reports an error of some sort. The weird part is it reports an error an different times though (The backup was 5 minutes from completing once!) Anyway, you guys really seem to know a LOT more than me. I would GREATLY appreciate some advice. Thanks!
Mike
(4 years, 4 months ago)
guess no one reads this thread anymore? :(
(4 years, 4 months ago)
If everyone would just use Linux there wouldn’t be any of these problems. Linux doesn’t have any of these disk issues..
(4 years, 4 months ago)
read it!
it seems clustersizes are wrong, get partitionmagic to adjust it!
(4 years, 3 months ago)
this is a question not a comment, i am ahving chkdsk problems, my system keeps saying there is a check dick scheduled for next reboot so it wont allow defraging of my windows partition witch is my C:/ drive on the first disk. i can defrag any other drive and such but not the primary drive because it always says theres a chkdsk coming on next reboot, if you have any advice please do tell
(4 years, 2 months ago)
Sounds like a lot of different problems out there, which tells you a lot about the stability of the Windows file system. Well, I have a couple of tips in this area. #1, if you’re using a removable ATA or SATA bay for your HD (especially a cheap one), try removing it and going direct to the controller. #2, it seems to be common on certain systems with large drives (at least on my systems which utilize Nforce2 chipsets) to develop index and security descriptor errors. Mine were related to the cache, specifically. If you have your option set to view hidden files, I believe the directory is c:\windows\prefetch. It is safe to delete the files in this directory, however, the errors will continue as you reboot because the functionality is still on. If you want to test your system to see if this is what is going on, open regedit. Go to {HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Memory Management\PrefetchParameters\EnablePrefetcher}. If you set the value to 0, then delete the files in the prefetch directory, then reboot, it will turn prefetch off. If this is your issue, you should be able to run chkdsk or NDD without any errors. The prefetch values available are as follows: 0-disable 1-app launch prefetch 2-boot prefetch 3-both 4-reboot
(4 years, 2 months ago)
Strangely enough, if I open a command window and run chkdsk without changing from the default directory, I get this: Correcting errors in the master file table’s (MFT) BITMAP attribute. Correcting errors in the Volume Bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these.
But if I change to the root directory first, no errors are reported. Anyone else seeing this?
(4 years, 1 month ago)
I am having exactly the same problem as Mike. Norton Disk Doctor keeps saying “Not Fixed” in red text after scanning for errors. Sometimes it even says Indexes “Not Fixed”
To try and fix the problem I did a Zero-fill format on my drive (it took about 6hours!!).
I reinstalled Windows and other software that I had before the format. In between installing each peice of software I ran Disk Doctor from the cd in Windows. It said “OK” for everything.
I then installed a load of Windows XP updates from the Windows Update site (including SP1 - which took 4 hours!) and then boom - Security Descriptors “Not Fixed” again.
Although I am not noticing any slowness or problems, its annoying just knowing something ain’t right. You try to look after your pc by keeping it up to date, and it still messes you about.
Anyway, I beleive that there is a bug in one of the windows updates that is causing this “problem”. Also I have heard that it could be nVidia display drivers that cause the problem, so if any of you have an nVidia cards that could also be the problem.
I have even thought about converting to Fat32 and then back to NTFS to see if that fixes it, but I really don’t want to spend another entire weekend doing so…
(4 years, 1 month ago)
If it is a problem caused by a Windows Update, Microsoft had better resolve it in SP2 which is coming soon or by a single update to fix it.
(4 years, 1 month ago)
I have norton disk doctor installed and after running the utility it say’s there is a problem detected on the disk.’security descriptor’ issue. I ran the disk doctor again and the problem is still there. What should I do to remedy this? Steps tried : Chkdsk, sfc /scannow, system restore. Any help will be greatly appreciated. Thanks
(4 years, 1 month ago)
I have the same problem. My system is a giga-byte pro mb (nvidia Chipset), 2 SATA 120gig Striped (240gig). and an 80Gig Seagate Ata Hd. This has happened to me a few times now. I originally thaught it was my raid configuration. but now the drive won’t even format correctly. I get a similar problem with my seagate drive. I go to install windows and when it finishes copying files, and restarts… it boots up to the seagate and said operating system not found. I havn’t tried a low level format on that drive but i do know Mandrake linux installs and boots fine on this drive(thats what I am using now).
Does anyone know if there is any software that will work on sata stripped raid configurations to format to fat32 or even ntfs?
(4 years, 1 month ago)
Hello,
my feeling is that there could be several different reasons for the problem with the volumebitmap, which occured on my Dell Optiplex GX 270 from one day to the other on drive c:. Nothing helped since I tried to stop all unneeded processes and services.
After I deactivated the “GhostStartupService” the problem was fixed.
Just try.
(4 years ago)
I have the same problem here with the security descriptors error showing up in XP pro with SP1a and all patches installed on two seperate machines with clean installs. I had the same error on all my previous installs. It doesn’t affect anything and both machines work perfectly. I just ignore it at this point. It’s a Windows glitch and I gave up trying to find a solution to something that doesn’t have a solution.
(4 years ago)
I’m getting a new disk - not a Seagate one.
I did another zero-fill on my disk using the Seatools Diagnostic utility, and then formatted to FAT32, then I installed Windows XP and did the updates. Everything was fine.
I go away for the weekend and come back to “File Structure” Errors.
So now I format to NTFS using “convert C: /fs:ntfs” in command prompt. Fine.
Then quess what… “Security Descriptors: Not Fixed”. “What have I done to deserve this?”
I’ve come to the conclusion that it is not a Windows bug, if you have the “Security Descriptor” problem it means your hard disk is knackered. I’ve only had mine for about 2-3 years.
I tried running Norton Disk Doctor on a different computer with XP and all the latest updates and there were no problems at all. Everything was listed as “OK”.
(4 years ago)
Mark, you don’t think it’s a Windows bug even though the Microsoft said it’s a Windows bug? I read some information over at annoyances.org and they basically said it’s a bug also.
I’ve installed XP Pro on a few different brand new drives and this error showed up time and time again.
Either way, doesn’t affect anything from what i’ve noticed, no crashes, my free space shows up correctly, have no problem defragmenting, or running Partition Magic 8 or any program for that matter.
Give it some time and the different computer that you’re talking about that is ok will show these errors.
It’s a Windows bug. I know my hard drives aren’t knackered, been down that route, it’s isn’t my drives.
Anyway, have fun trying to solve a problem you won’t solve.
(4 years ago)
It would be interesting to see which manufacturer everyone has. I currently have a Seagate ST340810a 40gb; this is the one with the “errors” on it. We could see if it is just Seagate drives that have the “problem” or if it is just any old disk manufacturer so let us know which disk you have.
I have just spent 3 and a half hours doing Seatools’ In-depth analysis and it showed up with no problems what so ever, so I am inclinded to go back to my previous thoughts that it may be a Windows glitch or bug.
Anyway I have ordered a Maxtor Diamond Max 9 120gb but I may just send it back…
(4 years ago)
Sorry to double post but…
Can you also state whether you have Norton Anti-Virus installed because this webpage says that NAV “resets security descriptors” so the problems may be due to that.
Let us know.
(4 years ago)
I have an 5 months old IBM Thinkpad with a Toshiba drive. I get the same Volume Bitmap “error”. I started out by reverting the harddisk to what IBM calls “Factory contents” which means that the drive is reformatted, and all IBM software is reinstalled. I still got the error. I have been in contact with IBM and they sent me a tool called Drive Fitness Test. I checks all physical aspects of the drive - NO ERROR. The problem is definately a bug, and not a hardware issue. When NT5 (Win2K) was developed, changes was made to NTFS. Amongst other things to support larger drives. It looks like the problem can be traced back to that time… - Just thought it could be helpful.
(4 years ago)
For all of you who have posted suggestions and comments on this issue I thank you for your input. I have been working on this issue for a couple of months now with several different machines. Some are older, some newer. Most of the issues I get are partition improperly dismounted and dirty partition flag set. I have been running W2K on these machines and keep getting the same result on many of them. These machines have assorted drives including Maxtor’s, a quantum bigfoot, different western digitals, seagates and others. It appears as though it is strictly a Microsoft issue and not a drive manufacturer’s issue. Every program that I run on the drives have all indicated that there are no problems with drives themselves, but with the way Windows handles the file allocation system. BTW I have some that have the different NAV systems and some that do not, so it could be related due to the fact that I have swapped drives and used one to fix the other for a miriad of problems and it could transmute from one to the other.
I purchased a new system back around 2K with 2K Pro installed on it and until this point in time had never encountered this problem with it. I am beginning to wonder if there might not be a virus/worm floating around out there that might be causing this problem on so many drives. After all, I have considered that Microsoft should change the name from Windows anything to Virus Haven a long time ago. Bill Gates messed up back when he let the almighty dollar rule him after about MSDOS 6.2 and started hiring all the hacks (notice I did not say “hackers”) that he currently calls programmers instead of providing people with what once was a good product.
I wish everyone the best of luck and if I come across anything that really helps I will post again.
(4 years ago)
I ran Check Disk from Windows (XP Home ) Explorer on my C: Drive (Maxtor 120GB partitioned into 3 drives) to fix file system errors. The program reported chkdsk would be run at reboot. While rebooting chkdsk reported “Checking file system on C The type of file system is NTFS Cannot open volume for direct access Windows has finished checking the disk.”
I got this report from Norton Disk Doctor (NDD) (Norton SystemWorks 2003 Ver 6.01)
When Norton Disk Doctor was run with ‘Fix errors’ checked, I was prompted to reboot and chkdsk reported as above “Cannot open volume for direct access ….”
As an experiment, I defraged the C drive which may have rewritten the Volume Bitmap and the error message disappeared from Norton Disk Doctor, although chkdsk still could not access the C drive to complete the normal checks.
Several days later, during an upgrade of ZoneAlarm from version 50590043 to version 51_011, the instillation required a system reboot to finish the installation, and chkdsk started to run (as it had failed previously, it was still scheduled to run at each restart) and completed the tests on the C drive with no problems. So did ZoneAlarm prevent chkdsk from accessing the C drive or was it just a coincidence?
(4 years ago)
Yes Phill, Zone Alarm 50_590_043 does stop chkdsk from running at boot time. It is a known bug in 50_590_043.
Mark
(3 years, 12 months ago)
This post & comments have been invaluable to me.
I have the same original problem Mike Steinbaugh reported.
I have it on a new HP Pavilion a450n system purchased 5/28/04, with a 160GB Seagate Hard Disk Drive (HDD). It originally manifested itself on XP Home Edition, and I noticed it originally when Diskeeper 7 reported it could not defrag the disk. I still had the problem when I upgraded XP Home to XP Professional.
Originally I thought I had a bad HDD; however, I bought a new HDD, 250 GB Western Digital, and made it the System Disc (Disk 0). I then reinstalled the HP provided software, so I could have the programs that came on the system. With just the HP provided XP Home software and other programs I still had the problem. However, when I checked the orignal HDD, now a slave, it does not have the CHKDSK problem it originally had.
The original HP software install that I have does not have Diskeeper, and I uninstalled the Norton Anti-Virus software. Both of these programs have been mentioned as possible responsible programs. Neither are a factor in my current situation.
After reading the post & comments I tried several of the suggestions:
I have researched MS TechNet using the clues and hints in the post & comments with no luck.
I have not experienced this problem on my Dell Inspiron 8200 laptop, received 1/03, Dell loaded w/ XP Professional.
I never saw this problem on Win NT 4.0 Server/Workstation or Win 2000 Server/Workstation in an NT 4.0 Domain during almost 5 years of administering it (one comment suggested this problem was prevalent in Win 2000).
My conclusions: - It is not a HDD problem - It is not a 3rd party software problem - It is a Windows XP, Home & Professional, problem.
Recommendation: - I do not have any. I still have this problem. Maybe MS will fix this with XP SP 2; but I will not count on it. Since Mike S. received an answer from MS Tech Support that I am unable to locate on MS TechNet I conclude it is another MS problem being swept under the rug. I downloaded Win XP SP 2, once I complete my reinstallation & setup I will install XP SP 2 and I’ll report back if it seems to correct this problem.
(3 years, 12 months ago)
I downloaded the Service Pack 2 for XP Pro and I still have this problem, system file errors with Chkdsk. Looks like were all gettin fu**ed the hard one about this w/out consent from Microsoft. Thanks Mr. Gates for another great OS.
(3 years, 11 months ago)
I recently put Windows XP Home on my home machine after having XP Pro from the Action Pack installed. I let me Action PAck subscription run out - so I had to install a licensed OS. I never had 1 problem with my disks under XP Pro. Now, about every other day, when I run a check disk - there are file system problems, MBR Problems, etc. Sometimes when I open IE, is finds problems with the files in the Temp folders and sets off a flag.
Thanks MS. You got us by the ba**s.
(3 years, 10 months ago)
The Security Descriptors problem is caused by all Nvidia display drivers.
(3 years, 10 months ago)
I’m wondering if this is a problem with XP and large hard drives used as the system drives. I’ve seen various posts in various places, and this seems to be a factor that many, if not all, have in common. I’d be curious to see if anyone has this problem whose disk is, say, only around 40GB.
(3 years, 10 months ago)
David, my drive is 40gb (37.27gb).
And Kejuan, I have 2 pc’s, one with Nvidia graphics and one with ATI graphics installed, the one with Nvidia is the one with the problem and the ATI one is fine, so I think you’re right my friend. I have also read somewhere else on the internet that Nvidia drivers are the reason for this problemo.
J.P.
(3 years, 10 months ago)
I have all these problems above - lost the ntoskrnl and /system/ eventually. Running 200GB Maxtor and NVIDIA drivers.
(3 years, 10 months ago)
You know what. I thik Windows 95 works better that anything out now. Just seems that everytime MS comes out with something, they keep screwing pooch. Oh, we the consumers are the pooch. Should have left well enough alone. My CHKDSK wont complete a check. Even safe mode, it states the same as in windows “cannot yadda yadda yadda” would you like to yadda yadda yadda on reboot of your system y/n. then on rebbot, it states that chkdsk shut down. hmmm go figure. well lets see CHKDSK dont work, and beacuse of this problem defraging is out of the question. Any solutions out there??????
(3 years, 10 months ago)
OS X or Linux :)
(3 years, 10 months ago)
xp
(3 years, 10 months ago)
I have Windows XP. Cant use defrag, because it states that “DISK DEFRAGMENTER HAS DETECTED CHKDSK IS SCHEDULED TO RUN ON VOLUME (C). PLEASE RUN CHKDSK /F” How do you turn this off?? If you tell te computer to run chkdsk it states ” THE DISK CHECK COULD NOT BE PREFORMED BECAUSE THE DISK CHECK UTILITY NEEDS EXCLUSIVE ACCESS TO SOME WINDOWS FILES ON THE DISK. THE FILES CAN BE ACCESSED ONLY BY RESTARTING WINDOWS. DO YOU WANT TO SCHEDULE THE DISK CHECK TO OCCUR THE NEXT TIME YOU RESTART YOUR COMPUTER Y/N” This does not work as well. The same thing happens. If you go to the command prompt and type chkdsk it states “THE TYPE OF FILE IS NTFS. CAN NOT LOCK DRIVE. CHKDSK CANNOT RUN BECAUSE THE VOLUME IS IN USE BY ANOTHER PROCESS. WOULD YOU LIKE TO RUN CHECK DISK THE NEXT TIME YOU RESTART THE COMPUTER Y/N” If i boot into safe mode with prompt and type the same thing “chkdsk” it states the exact same thing. I really dont care about chkdsk, i just want to be able to defrag the drive when i want to. So how do I go about solving this whole issue?? Whatever happened to WIN 3.1 and WIN 95. I dont ever remember having problems with these systems. Heck, even back the other company’s had shells that worked better than windows, just too bad i cant remember them :))
(3 years, 10 months ago)
I’d be curious to see if anyone has this problem whose disk is, say, only around 40GB.
I’ve got two computers here at my business. I’ve had these problems on a machine with an 80GB Samsung drive but not on a Toshiba laptop with a 20GB drive.
Uninstalling NAV (switched to AVG antivirus) seems to helped a little—the problems are slower to re-develop—but not stopped it altogether.
(3 years, 10 months ago)
Wow! This thread is old!! And still no solution yet… That sucks!
I have the volume bitmap error on an XP SP2 machine running Oracle Personal Edition 9.2. Everything went fine till this week. Oracle crashes due to rollback error!
I then tried to find the error…
First of all, it’s NOT the nividia thing! I have an SIS graphic adapter. I did NOT make an low-level format and I won’t do it! This doesn’t solve anything. Wanna know why?
I went through the whole installation prozess of XP SP2 (service pack on installation CD) and made an image of the disk after every step.
After a clean new install of XP everything is fine, no chkdsk-error. (XP SP2, 1 primary partition with 75GB on a 80GB seagate disk)
I then installed all the drivers available for my system configuration and still no chkdsk-error (no windows patches installed).
Even after installing software like PCAnywhere, McAfee Internet Security and Acrobat Reader everything is fine. No filesystem errors.
But after the installation of the Oracle Personal Edition I get those volume bitmap errors! A reboot with a full chkdsk doesn’t resolve this!
When I then switch back to any of the non-error versions of windows, the error disappears! So it is NOT an hard disk problem! Performing the seatools diagnostic with full surface scan on the harddisk verifies this assumption.
I noticed that before the oracle installation chkdsk performs a lot quicker. But since Oracle need 3 installtion CDs this should be normal.
I found that nearly all Windows XP machines (SP1/SP2) report this error using chkdsk. But most of them are working without problem.
My problem child with the Oracle does so too! But only for a week or so. Then the database chrashes! This is the second time this happened! As far as I can remember the last crash was on an SP1 machine. So this should not be the source of the problem…
This is where I stand today. I’ll continue searching the source of this error but maybe this helps you a little bit…
(3 years, 10 months ago)
Can’t you people see that the “errors” are caused by Nvidia chipset driver versions 46.xx and above. ATI users are fine. If you have ever had Nvidia drivers installed and working on a hard drive with the errors, they will not go away unless you do a low level format. If you don’t want these “errors” switch to an ATI chipset.
(3 years, 10 months ago)
Can’t u read? Neither is this an nvidia driver problem, nor is it solved with a low-level format!
I think it’s just a chkdsk error because it’s designed for FAT and can’t cope with NTFS. (I read advices never to use chkdsk in windows higher than 95!)
I get the volumen bitmap error but still can do a defrag without any error messages!
The only thing chkdsk says, is that there are references to empty spaces in the MFT. This is because NTFS keeps a backup of those references even when files in this spaces are deleted. I don’t think, it’s really an error. Even though so many people have problems with machines reporting this error… That includes me!
Correct me if I’m wrong (only well-founded assertions)…
By the way, after I did an defrag, the BITMAP attribute error disappeared!
(3 years, 10 months ago)
I can read. Can’t “U” spell? If you learn to spell and use the English Language properly, maybe people would be able to understand you. You can’t even spell your own name, Reggie.
Maybe if someone with the slightest bit of intelligence could say whether they have Nvidia or ATI drivers it might help resolve the situation. It doesn’t even matter any way.
The errors are not actually errors, just the Nvidia drivers causing the Security Descriptor cache to be reset at boot-time, everytime. We need a program that can read the cache in DOS before the OS starts.
As some people have said, and I have experienced it myself, sometimes Chkdsk and Disk Doctor report no errors at all.
(3 years, 10 months ago)
Since installing SP2 on my XP-home computer, the smart disk stuff on my HP Pavilion tells me it detects that my hard drive might fail. Running chkdsk & chkntfs, no problems are found and no dirty bit is set. Powerquest drive imaging software (v5.0) comes up with an error 1513, thus I can’t ghost the hard drive. I will go back to uninstall SP2 this evening and see where that leaves me.
(3 years, 9 months ago)
MAXTOR 250GB One Touch Firewire/USB copy problem Windows XP SP2, all drivers updated etc.
When I copy a nero image file from the external harddisk to an internal one everything seems ok and no filesystem errors reported with chkdsk, no dirty volumes.
But FC /B Gives three byte differences and strangely enough it’s alsways the highest bit of the lowest nibble (bit 3) that’s wrong. Wheter I connect the Maxtor via Firewire or USB makes no difference whatsoever.
I discovered this problem because of Nero reporting differences when burning a DVD with the image (or the VIDEO_TS directory) on the external medium, This resulted in several misburns! Sometimes the file seems the same but FC reports a difference in length.
(3 years, 9 months ago)
Follow up Copying a large file
Copying from internal to external followed by a FC .. /B Give four differences:
592A4742: 04 0C -> 0000 (0)100 vs. 0000 (1)100
9D6AB742: 4C 44 -> 0100 (1)100 vs. 0100 (0)100
ABD29742: 4A 42 -> 0100 (1)010 vs. 0100 (0)010
FBAA9742: 29 21 -> 0010 (1)001 vs. 0100 (0)001
And again, the same bit is different!
Next I’ll Try from internal D: to Internal C: to see if the problem persists.
(3 years, 9 months ago)
Follow up copying large files
Quod erat demonstrandum as mathematicians say
Copying from C: to D: followed by FC … /B gives the same problem. Maybe it’s some BIOS setting related with PCI bus transfers or it’s the OS itself. I’m going to look if there are known problems with the MSI KT4V on http://www.msi.com.tw
(3 years, 9 months ago)
Problem solved - it seems
Updated AMI BIOS from 1.5 to 1B0
Copy from E: to D: followed bij FC … /B - Ok
Copy from E: to C: followed bij FC … /B - Ok
Copy from C: to D: followed bij FC … /B - Ok
In version 1.7 some CRC problems were corrected:
From http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=362&kind=1
Version 1.7 Update date 2002-12-26
Update Description
-Support AMD Barton XP2800+ (FSB333) CPU
-Fixed system sometimes will have IDE CRC error
-Fixed D-bracket2+USB keyboard, cannot use keyboard on DOS mode.
Maybe this’ll help others.
W.A.Schreuder@home.nl
(3 years, 9 months ago)
I am following this thread now for a long time and i have the same problem in my german version of winXP with SP2. chkdsk finds the ntfs partition is bad because of the volumebitmap. Why is Microsoft unable to solve that plague??? Or are there any news i haven´t heard yet?
(3 years, 9 months ago)
I started having this problem a while back, mainly when I was burning high-volume CDs and listening to MP3s at the same time. It came to a head during a LAN party when I was forced to reinstall Windows several times during the event.
It then happened a short time later after the LAN where it decided to kill off Windows entirely. I was able to recover all my data through Linux and reinstalled Windows. Thinking it was related to the power supply (the general consenus from everyone I talked to about it), I took my machine in and got the 2year old 300watt supply with 500watt. Soon after that, the error occured once more but it wasn’t as severe.
I ultimately concluded it was related to my USB2 drive always being plugged in. So I only use it when needed and haven’t had anymore errors since (but the aforemention burning and music playing still happens occasionally, but I’ve weaned myself off it).
(3 years, 8 months ago)
Toshiba Satellite 1955-S801; XP Professional, SP2; NVIDIA;
Additional considerations: - i have a logon script that backs up files after i logon. - i sometimes use a ram drive (formatted as fat32.) - i use the subst command. - Microsoft Baseline Security 1.2 installed. - i am using an exteral keyboard and mouse via a USB port.
Same error about the Volume Bitmap when I run chkdsk from a command prompt. I run the boot time chkdsk; the first time after doing this, i get a message saying, “UNKNOWN HARD ERROR” no matter which application I run (including chkdsk.) After I reboot, I no longer get the “UNKNOWN HARD ERROR” message, but the volume bitmap errors occur again. This has been going on since SP1; and maybe even before. I am able to install software, but it frequently doesn’t work; and the vendor is unable to explain why; I suspect this is probably the cause; since everything else seems to be functioning properly.
This is obviously a colossal pain in the**** I am a developer and make my living with my computer, and am unable to install some software tools that I really need. I have been trying to get by in the meantime, but am nearing the end. I will probably go back to Windows 2000 Professional, unless I can get a resolution soon. This is really the only place that seems to have others that are experiencing the same error. It is helpful to know that I am not crazy and have not done anything stupid to be causing the errors myself.
I have tried everything above but the low level format. Has anyone made any progress with this? Or have any suggestions on how to fix it?
Thanks, Jeff Dallas, TX
(3 years, 8 months ago)
Same Error here on a nforce2-chipset machine with nvidia mainboard drivers installed (ATI graphic card). I can’t run PerfectDisk’s offline defragmentation because of that error and chkdsk always shows up this Volumebitmap error.
:-(
(3 years, 8 months ago)
I have the issue too, where Norton says “security descriptors not fixed”. I’ve had this issue on both of my boxes, since the release of WinXP and with Norton 2003-2005. It only occurs on my boot drive where I have WinXP installed.
I recently did a low-level format, and that didn’t solve the problem. I thought I was running into the old 120GB limit, since my hard drives are 160GB Maxtor. But I use a Slipstreamed WinXP SP2 disc, and immediately apply the Maxtor registry patch for large drives over 120GB.
When I get home, I’ll try disabling write caching, but I doubt it will fix my problem. Otherwise my system seems to be doing okay, besides the error “Security descriptors not fixed.”.
(3 years, 7 months ago)
To avoid getting “Security Descriptors = Not Fixed” errors, Do not delete files when they are in use, for example; do not clear your “Temporary Internet Files” cache whilst you have Internet Explorer windows open, and do not delete pictures whilst the preview is still coming up etc.
If you do delete the files while they are in use, the security descriptors for that file (or those files) will not have a file to associate themselves to, therefore meaning errors in the file system.
Mark
(3 years, 7 months ago)
…and the same applies to uninstalling programs using “Add/Remove Programs” in the control panel, make sure the program you want to uninstall is not running when you uninstall it!
(3 years, 7 months ago)
Hello, I’m actually experiencing the same kind of problem on a XP Pro/SP1 box. It apparently started suddenly (Machine’s not mine). I performed every check I knew of and I’m convinced it is indeed a software issue. Most probably Windows’. The following article is ample proof -if ever needed- that M$ people can screw things up on their own: http://support.microsoft.com/default.aspx?scid=kb;en-us;235771 Althought I don’t think it applies to anyone in this thread, it could give ideas to some of you MVP-M$-certified-something. As for my client, I occulted the problem using CHKNTFS /X C:
(3 years, 7 months ago)
As an afterthought, some clues lead me to also suspect -at least in my case- the Norton AV Recycle Bin protection feature (That incidentally runs as a service, too).
(3 years, 7 months ago)
I’d just like to direct everyone’s attention to a thread in another forum linked to this subject, perhaps some of those users may be able to help aswell - I think I’ve given a good enough description of the problem most of us are having.
(3 years, 7 months ago)
Hello.
Three days ago I noticed the same problem with chkdsk reporting volume map errors on my laptop (XP Home, 80GB), and after a full day spent with a clean reinstall of everything it was still there. Checked out my office computer (XP Pro, 40GB) and the same error showed up as well - God knows for how long it has been there!
After a few hours avidly searching the net for it, it looks like a software bug in Win XP that only occurs on NTFS file systems - any other connections with drivers, etc. don’t look founded to me - and it seems to be nevertheless harmless, but anyway annoying to be there.
The only solution that worked in my case is the one described here by [Chilln (June 4, 2004)] - see in the forum above for solution description. Disabling the Windows Prefetch worked miracles for me. Thanx Chilln and I strongly urge the rest of you guys to consider this - it really may work for you too!
(3 years, 6 months ago)
I decided to fresh install win2k SP4. And I faced the same problem. In the past, I never faced these problem.
I will try to setup %TEMP% and %TMP% outside the user profile directory.
(3 years, 6 months ago)
I tried the prefetch thing and lo and behold it gets rid of the volume bitmap message when I run chkdsk. If I enable it again however the message comes back. What gives? I also have an indexes error in Norton Disk Doctor that does not show up in safe mode. I am beginning to think NDD is getting it wrong more than it gets it right.
(3 years, 6 months ago)
I have spent weeks chasing down the Security Descriptor error and file system error noted in Norton Disk Doctor. I can’t tell you how much sleep I have lost worrying about this problem, which as it turns out, is not a problem at all. OK, here goes….. When Chkdsk /f finds and cleans-up unused index entries it is simply a normal house-keeping function. Microsoft intentionally does not report the housekeeping because it is just that, housekeeping. The only way to find out about this routine housekeeping is the view the winlogin in the event viewer. I must thank everyone for all their posts to this forum and other forums about the Disk Doctor glitch. Especially helpful were the posts suggesting you should turn off the indexing service, prefetch services and the posts about changing your IDE drive settings to PIO from DMA. These posts got me thinking that this problem is just a disk caching problem. I noticed that if I ran Disk Doctor and got the page that said the disk had errors on it but immediately ran Disk Doctor again, then Disk Doctor would very often report the disk had no errors. Taking into account that most hard disks now have very large caches of 2 to 8 MB I decided to run an experiment so simple even I doubted it would work. I open up the Norton System Works program and then migrated to the Disk Doctor Splash Screen. I checked off the disk I wanted to check for errors which in this case is the system disk or disk C. Then I waited one minute before actually starting the Disk Doctor program. Disk Doctor is started when you select the Diagnose Button. When I waited at least one minute to start diagnosing the disk after opening the program spash screen, then Disk Doctor would always tell me the disk was clean and had no errors. So the problem is not a Windows XP problem, the problem does not indicate your disk is bad, and given when Disk Doctor was written, is not even a problem with Disk Doctor. The problem is simply a disk caching problem. When you open the Disk Doctor Splash Screen, info is cached to the disk that is written back to the disk as the program is running if you start Disk Doctor almost immediately after opening the Disk Doctor Splash Screen. If you don’t want to wait a minute for the disk cache to catch-up with the system, then you have to disable disk caching or the write behind capabilities of your disk. It really is that simple. And, it is so simple it freightens me. So to recap, this is not a problem but normal behavior on an NTFS system drive. See MS article ID# 109524 regarding NTFS file system behavior. None of us would not even be aware that Chkdsk would clean unused index entries as a housekeeping process unless we had spent countless hours trying to find out why Disk Doctor kept returning reports of disk errors. So try waiting a minute before starting to diagnose the disk. When everything comes back normal go to bed tonight and sleep well like I am going to do for the first time in more than a week.
(3 years, 5 months ago)
Nice idea about the cacheing. Works for you but not for me. NDD still shows a security descriptor error starting it several minutes after the splash screen goes away. I’m in the process of bugging MS about this and will post their response if they ever get around to it. Since they exported their support to ASIA, I’ve been getting extremely polite but uninformed answers to questions about SP2. BTW, I seem to be getting the Bitmap Fixing Error Chkdsk message after another message saying that it’s corrcting a Usn segment. Anybody getting this. Also, I have 5 machines running XP all getting it and two running 2000 and NOT getting it.
(3 years, 4 months ago)
I have a removable USB drive that is 60GB. I heard when I got it that it was advisable to use the NTFS file system, so I converted what was a FAT32 system to NTFS. The only problem is that I have a laptop, and I am always unplugging my devices from my computer. NTFS isn’t removable friendly. So I decided to switch back to FAT32. But since XP won’t format drives larger than 32GBs im stuck. How can I format my drive into FAT32 if it is 60GB? Someone mentioned in this forum about using a Win98 book disk, but I’m not exactly sure how to do that. Please inform.
(3 years, 4 months ago)
also DOES happen with ATI cards installed in the machine.
(3 years, 4 months ago)
I am having the exact same issue as above, same drive too. Its actually on a friends ‘puter, He got this wd250 (I also have one as well) and gave it to me to fill with music and movies and stuff. I have reformatted the **** thing numerous times, gotten a new drive from WD and even done the low level format. Whats odd is I have no problems on my machine (SPsp1), furthermore I have 5 large drives all on this system and problems. His is another story. He has XPsp2 and nothing seems to fix the issue. I noticed it only seems to happen to the mp3 files, at least recently, i know at first there was a problem with video too.
Waht i want to know is are there any others out there who are having these specific issues?
(3 years, 3 months ago)
I have been getting the same errors as Mike Steinbaugh. I just found the cure for me too. I used Partition Magic 8.0 and converted my 127gb C: partition and my 22gb D: partiton from NTFS to FAT32. No low level format, no loss of data, just convert to FAT32 on the fly with PM 8.0 boot disks. No more chkdsk errors.
(3 years, 3 months ago)
I highly recommend against converting to FAT32 over NTFS. NTFS is a much more stable file system, even if it does report a CHKDSK error for some people. FAT32 is not designed for large hard drives and has a tendancy to accumulate bad sectors easily.
(3 years, 3 months ago)
Too late, It’s already done. I’ve left my 2nd HDD as NTFS as that never shows errors when I run chkdsk /f. I had a friend run chkdsk /f on his NTFS C: partition tonight and he got the exact same error report as me. NTFS is not cleaning up after itself or something so I’ll see how it goes with FAT32.Of course Microsoft says XP doesn’t support FAT32 partitions over 32gb but that is BS and I’m running a 130gb FAT32 partiton right now. Only problem is that Partition Magic made such a mess of of the files when it moved the data and converted to FAT32 it is taking forever to defrag. But once that is done I will see how it goes and check for bad sectors on occasion. I’ve never heard of FAT32 causing bad sectors. Drives going bad cause bad sectors and not the file system. I’ll keep it in mind though as there may be something to it. I can always convert back to NTFS.
(3 years, 3 months ago)
“Same error about the Volume Bitmap when I run chkdsk from a command prompt. I run the boot time chkdsk; the first time after doing this, i get a message saying, “UNKNOWN HARD ERROR” no matter which application I run (including chkdsk.) After I reboot, I no longer get the “UNKNOWN HARD ERROR” message, but the volume bitmap errors occur again. This has been going on since SP1; and maybe even before. I am able to install software, but it frequently doesn’t work; and the vendor is unable to explain why; I suspect this is probably the cause; since everything else seems to be functioning properly.”
I have this IDENTICAL problem.
(3 years, 3 months ago)
I’ve read this thread carefully and let me add I have the same problem. I am running DFI Nvidia4 motherboard and 2 160GB drives Hitachi drives in RAID 0 configuration and one WD ATA drive. After reading all the posts it seems like a caching/Nvidia problem to me.
(3 years, 3 months ago)
Is this the answer?
“Correcting errors in the Volume Bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these.
Tis is a known issue and the error messages are not actually means that there is problem in your system. You can safely ignore the error messages. The reason you are seeing these errors appear is because when you run CHKDSK in command prompt, it runs in “Read only” mode, and the state of the computer is changing at the time you run the utility. A “read only” chkdsk on an active NTFS volume will result in false positive errors, this is normal.
Read-only CHKDSK will abort before it completes all three phases if it encounters errors in earlier phases and is prone to falsely reporting errors when in read-only mode. That is, CHKDSK may report that a disk is corrupted even when there is no real corruption present. This can happen if NTFS happens to modify areas of the disk on behalf of some program activity that CHKDSK is examining at the same time.
To verify a volume correctly, the volume must be in a static state, and the only way to guarantee that state is to lock the volume. CHKDSK only locks the volume when it runs before entering Windows or in Recovery Console with /F or /R (which implies “F”) is specified.
To verify this, you can restart your computer in Recovery Console and run “CHKDSK /f” in there. See if you get any error messages.”
(3 years, 2 months ago)
I wonder how much M$ would have to cough up if a judge made them pay us all for the cost of our lost time on JUST THIS ONE inexcusable problem?
(3 years, 2 months ago)
Same problem with a wd 112gb drive that is running win 2k server on a machine that originally had the hard drive formatted for xp home by dell (dimension 8200) with nividia chipset. I wonder if it is the NTFS version used by xp home that is responsable as I never had the probelm with a win2k formated ntfs drive. As I am unable to defrag I used robost file copy to backup my data and loaded 2003 server on the drive with a fresh partition (note: their was a unmounted 32mb fat partition on the drive from dell) and no problem afterwords. ALso in win 2k their is no prefetch descriptor in the registry. There was no write enabled caching on the drive. I used both Norton disk doctor, diskchecker as well as other utilities which all came up with the same volume bitmap error. occasionally I also get index $I30 errors on various files as well that diskchecker will correct efven when the fix atribute is unchecked. although you have to run it several times (suggested with out the surfacecheck) to get the progam to run with out errors. Only aftewhich I can defrag. Also I dont use Norton antivirus, I use Macafee Sonic wall ASP antivirus, and dont use norton system works. (this is not an atrifact of norton but a bug in the way the MFT is being addressed by the NT OS to allow sharing of files simultaneously (hence the term ntfs new technology file system) as opposed to dos (disk operating system) and FAT (For file allocation table) which cant address over 16 bits of addressable memory which limits the size of the drive it can handle. (as does the 32 bit FAT (n although it is significantly larger drive. I think that microsoft stripped down xp home and this is one of the side effects and a good reason not to copy a disk image created with xp home onto a xp pro prepared system. none of my denovo workstations with xp pro sp2 have this problem.
(3 years, 2 months ago)
Hey all,
I had the dirty bit error which would prevent defragging. I managed to resolve it by first using chkntfs /X to unschedule chkdsks upon startup, then I moved the pagefile to another partition which in turn allowed me to complete a chkdsk /f /r on the partition with the dirty bit.
Once that was done, a defrag of the dirty bit partition was successfull completed. Dirty bit is now gone. Note that luckily it wasn’t on C: drive for me, so this solution might be only for people with problems not on C:
(3 years, 2 months ago)
Running checkdisk from the command prompt it appears will yield basic results. The drive needs to be locked and chkdsk /f be performed, but windows will not let you lock the drive.
Therefore when I had this problem I forced the dirty bit on “fsutil dirty set c:” because windows xp defaults to chkdsk /f on boot if the dirty bit is set.
I had a clean repair as evidenced by bootex.log which chkdsk creates.
(3 years, 2 months ago)
Wow!
Had same problem on a Toshiba laptop with WinXP home sp2 “all current updates installed 6/16/05″ 100gb hd, and ATI drivers runs fine. Noticed this problem ’security descirption poop” occasional but would disapear after reboot chkdsk . Today it did not “after chkdsk in safe as well” and thus my journey began. This was a great log to find. Anywho, I started a defrag with norton speed disk and then found this page in the mean time and I read through all the posts. My defrag finished fine and I ran the scan disk right after “I did wait 2 minutes before running after it loaded as mention in a previouse post” with disk doctor and it came up clean. Then rebooted and ran the disk dr again “without waiting a few minutes” and security description poop popped up again! Did not even close the program waited 3 minutes and ran it again and it is “OK”, Do it again ” maybe a minute wait and its not. Reboot again load Disk Dr. wait 2 minutes and its fine again.
My vote it is a caching issue of some sort I do not care to understand. It works and I will leave it at that. It is still annoying and I relate to you 5am frustrated peeps. I have not been this frustrated since win95. “If it aint broken don’t fix it” Good Luck to all.
(3 years ago)
Hi All,
Came across the same or similar problem last night. My home built XP SP2 machine kept running chkdsk on f: at boot. My 200gig WD is partitioned into c:,d:,e:,f:,g:,h:, and i:. Partitioning was done with a win98 boot disk prior to the installation of any OS. The problem started when my machine shut down unexpectedly while linked via WiFi to my win98 laptop. I believe that I was trying to acces f: on this machine when it crashed. Ran chkdsk f: /f in safe mode and rebooted. The problem jumped to g:. Again in safe mode ran chkdsk : /f on all drives. Problem went away. I hope this helps you all find the particular glitch.
(2 years, 11 months ago)
I have Diskkeeper 7.0 and professional XP, 100Gb drive partitioned c and d and I have experienced a problem with defragmenting drive d as I keep getting the message to run ChkDSK at next reboot but ChkDSK doesn’t reveal any problems and I get the same message when trying to defrag drive D. I get the same message when I try to defrag on reboot. The only way I can defrag D is through Diskkeeper’s setdkacls.bat by setting the prompt to setdkacls d:, however, you cannot see the visuals. Any solutions?
(2 years, 10 months ago)
I am having the exact problem on an external hard drive (Toshiba 80 GB) of the system which has Windows NT 4.0 (Service Pack 6a) running on it. There is a single application which writes and deletes files to the external drive. After weeks of verification, the application does nothing wrong but when the application is writing and I run chkdsk it gives me the MFT or Bitmap errors. When I stop the application, I see no error messages. My Problem is: this external drive boots up the system and on an improper shutdown the system does not reboot. I used DFSee to analyze the hard disk and see the same MFT and Bitmap errors. So I am convinced that this temporary inconsistent state which NTFS goes into when writing/deleting files if not handled properly (not terminating gracefully on shutdown) will definitely cause the system not to reboot. Because NTLDR checks the file system sanity before booting up and when it finds this inconsistent state, it is unable to boot up the system. And since this is NT 4.0 I do not even have an option to disable disk cache! Any ideas?
(2 years, 8 months ago)
I have been getting scandisk at startup every since I un-installed AVG Anti-Virus FREE Version. I did have (1) Virus in the Vault at the time of uninstall. I was promped to delete or ??? (store??) at the time. I choose delete. I believe that this is the reason for the constant report of (developed bad sectors) at start-up. However when I run Scandisk it reports no error’s found. Is it possible that AVG Anti-Virus has security marked a part of my hard drive and therefore reporting them as bad sectors at startup?
(2 years, 6 months ago)
I converted my windows xp professional drive from FAT32 to NTFS and restart the computer but it hangs up before windows start. I don’t know what to do. Any help?
(1 year, 11 months ago)
I gave up and just started using Linux. (Ubuntu / CentOS)
(1 year, 9 months ago)
Don’t close this thread!!! I have a new system (Asus A8N SLI Prem mb, 2 Seagate 320 drives, XP Pro SP2, NTFS) and didn’t even get all my programs on before getting “CHKDSK discovered free space marked as allocated in the volume bitmap” error and prompting to run Chkdsk /f which of course has to be run at next boot as the error occurs on the OS volume. I ran it and the error disappeared, but then came back soon after…very inconsistant. I wasted a bunch of time before formatting and starting over. This time I disabled Indexing on all my drives right after I got Windoze running. And guess what…after a couple days of reinstalling, problem came back! So I bought another drive (!) and started again! And…you guessed it! I wish I’d read this forum first!!! Anyway, I believe it is indeed related to disk write caching. I now tend to agree with those who say it isn’t a serious problem (no apparent problems with my system) (as long as system seems to run well otherwise, and defrag works, and free space and used space seem to add up to total drive size on all drives) But I’ve lost a week of time. And I’m disappointed Microsoft doesn’t even honestly address this issue on their website–even if they just clearly admitted it as a common “bug” or glitch, I might have saved a lot of time and some $$ (though I like having the 2nd drive to put all my data on, completely on it’s own disk, as far from the Windoze operating system as possible!
(1 year, 8 months ago)
But I find it can’t be ignored,because my space is diminished when it happened, and I want to get my lost space back. Can you find some resolution to deal with it.In a word,I don’t want to ignore .
(1 year, 4 months ago)
Thanks for maintaining this thread here. This problem is still around even until now, with all the service packs and patches released.
(2 months, 3 weeks ago)
epwvyxa pgank