I've gotXP/7 on different partitions. Partitions: C:XP(primary), D:Document(logical) and E:Win7(primary). I'm well conserned in computers but It was my first and failure experience with SECURITY and PERMISSIONS. ( 3 days Win 7 worked norm, I booted to XP and everything was great, BUT further more. On the day 4, I suddenly notised black wallpaper on the desktop(filewas from the Documents partition). In Win7 I had no permission to open it. Then I noticed that it conserned not only that file, but alot of folders(looking to be randomly chosen), soI DO have noaccess to themin my winXP. I've got my work files there. I don't know HOW to undo this sudden mess. Please give me a piece of help! + I fogot! I added the folder Document://Documents to the Documents library!!!These folders are NO longer in Documents Library, but the problem REMAINS! Report post as abusive

So if I'm understanding this right, "Document" is shared by both XP and Windows 7? Have you tried to 'take ownership' of the folders? Just a kind reminder, even dual booting with betas puts systems at risk. Ensure you have a backup of your work documents that is in an offsite location.

Yes,D:Document(logical)partition is well seen andfull(was before trouble) accessed in both XP and 7.Please, how to 'take ownership'? This is done in XP or 7? (It's my first experience with 7 and securiy and permissions)

I think you have corrupted your ability to gain access from the installed OS's on that system. I have noticed a lot of people trying to dual boot with the Windows 7 beta and then trying to share protected folders, operating system boot partitions, and system managed folders with either or both operating systems and essentially ending up with similar problems as you have now. First of all, the data, your work, is the most important problem now. You need to recover it. I would start with taking the drive out and installing it into a USB enclosure then using another computer with XP Professional, Vista for Business (or Ultimate) or Windows 7, try to recover your folders. You may have to take ownership of the entire drive or just the folders in question. Start from the root of the drive though, then browse to the lowest level folder in the tree and start taking ownership there. If this method fails, you should be able to recover your data with a data recovery program. After you have got your data back, you will likely have to either reinstall one of both operating systems as many hidden and system files will have corrupted persmissions on them. If you are lucky, and no media or third party secured applications were involved, you may be able to make new accounts then delete the corrupted ones using a file deletion tool such as Unlocker (http://ccollomb.free.fr/unlocker/ ). For future reference. the Windows operating systems has very clear instructions as to where to put files you wish to share with other computers. Remember that a dual boot system, from a security perspective is essentially like another computer accessing your data, it is not a good idea. Put any data and files you wish to share on a network file share, or at the very least, in the shared documents or in the public folder. The best solution is to use a removable drive and store them there. Do not point windows to that drive as your My Documents folder, or as where your user accounts are stored, that will cause the same conflicts with security. The problems you are having is by design in Windows. The solutions are simple of you think ahead. There are lots of Websites with a plethora of ideas and guides about how to share files with multiple operating systems. Do yourself a favor, don't just guess, do the research.Computer software consultant for 27 years

I have a similar problem to Alex. I am dual booting and sharing my Data drive with both operating systems. Why would this work fine for months and suddenly I am not able to access folders (or at least write to those folders) from Vista? So far I have been able to take ownership of the files and get access to them, but it is becoming very time consuming to do that. I dual booted between XP and Vista for several years with no such access problems. Are you saying that I cannot set the same folder asa document folder in both operating systems without running into permission problems? Could this have started with me activating the Home network feature in Windows 7? I have the same user name in both operating systems. Is that good or bad as far as permissions go?Thanks!

Here's a copy of a post I made in http://social.technet.microsoft.com/Forums/en-US/w7itprosecurity/thread/d14731ec-4f0e-4ef8-9aac-028dd7104e0eIt may also be relevant in respect of http://social.technet.microsoft.com/Forums/en-US/w7itprosecurity/thread/a092f176-b2f2-4b98-9e02-15d34d45b224"Here's another viewpoint, including something that "worked for me":Like a few posters here, I also found that whole logical volumes randomly became "effectively off-limits", with some of the obvious symptoms including:* The absence of the "New" context option when trying to create a new folder. Obviously, I couldn't create much of anything else, either.* Messages to the effect that a volume was write-protected.* Inability to create files into existingdirectories.Some configuration-related info (not trying to show off, just painting a picture):* Multi-boot setup: XPhome/32bit/SP3 (my old 'live' system) + Win7RC/32bit (a testing system) + Win7RC/64bit (another testing system) + Win7HomePremium/64bit (installed 2 days ago with the objective of going live) * I'm currently running with UAC turned off, because of various 'issues'** Multi-HDD setup (not all shown, but all those shown are NTFS): 'C' - Win7HomePremium boot, brand new Corsair SSD purchased for this install, never used esewhere. Not partitioned. 'H(ome)' / 'M(usic)' / 'V(ideo)' / 'W(ork)' partitions on new Raid1 matching pair in eSATA enclosure. 'E' -Win7RC/64bit boot volume. PATA.Other hidden partitions. 'F' -XPhome/32bit/SP3 boot volume. SATA. Other hidden partitions. 'G' -Win7RC/32bit boot volume. SATA. Other hidden partitions. 'T' - WD eBook. eSATA enclosure. Not partitioned. 'X' - A scratch volume.SATA. Not partitioned.* The symptoms:Ihad been doing the occasional reboot among various systems to check things out.During *one* of the boots into XP, I noticed CHKDSK being scheduled: I let it run. I forget which logical volume.During a Win7HomePremium session, SOME of my volumes,namely X, H, M & W (but not V) started to show the 'unable to create new directory' problem. I was already running with UAC off (because of a limitation in DriveImageXML).I tried following the "take ownership" suggestions: Generally seemed to fail because of "Disk is write-protected"I tried following the "attrib" suggestion: Seemed to 'process' for a while, but eventually failed saying that 'system volume information' was read-only (I think)* What "worked for me":Somewhere in a linked post, there was a reference to running CHKDSK, so I tried it with "Automatically fix file system errors"checked ONand *IT WORKED*...but... there may be some diagnostic info in the WAY that it seems to have worked: Normally, the little window for CHKDSK shows some status information like USN bytes processed, *and* it also normally terminates with a "... successfully scanned..." message. When run against my 'broken' drives it ended relatively quickly, didn't send any messages, but it certainly fixed my problem... for now... Subsequent reruns of CHKDSK against the affected drives run normally, with full status info messages. I guess I can't reproduce the problem, and I sure don't want to!* Comments:It looks to me as if the problem may be symptomatic of sometype of corruption at the logical volume level.I'm not a Wintel expert but I do have 30+ years in mainframes at fairly deep technical levels, so I'm not totally illiterate either... ;-)I'm absolutely amazed that there seems to be such confusion surrounding an undoubtedly serious problem affecting a major system that has been out in beta for months, on high-visibility public release for weeks,and the SW supplier sems to be s.o.o.o quiet about it all...I think I'll try and avoid booting XP again... unless it's to revert because my Win7'production' system didn't come up to scratch :-) :-)Good luck to everyone having this problem; I hope my experience helps."

My latest update (from http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/dbdf9e52-8eb9-4a4f-a10e-2764dc20596d):"I think I've found MY problem; not too sure wheher it's going to be the same for you.In my case, some drives were randomly going into write-protect, and running CHKDSK was one way out of the problem, but only temporarily.On some occasions the CHKDSK would end quickly without any message(s), sometimes it would fail with 'An unspecified error occurred (696e647863686b2e dee).'Either way, the write-protect problem usually went away, but it also came back after the next boot, not necessarily on the same drive(s).The drives that were randomly going into write-protect were all connected via a GBB36X ( rebadged JMB36X) controller chipon my GA-P35C-DS3R m/b, with chipdriver version 1.17.42.8 (Win 7 couldn't find a later driver).There was a fix at 1.17.43 which seems to address the problem.I think MS should make sure that the driver update can pick up a later driver, and Gigabyte should also do the same!"R1.17.43WHQL (11/17/08') - Fix the issue that system event log has error #117 in Vista. - Burning disc sometimes failed with some IDE ODDs on some platforms. - Snake TB-400S PMP hotplug failed. - Fix the issue that hard disk becomes write-protected sometimes on the platform equipped with 4GB DRAM."If you have any flavour of the JMB36X chip, maybe you should try updating your driver from http://www.jmicron.com/Driver.htmIf the problem comes back on my system, I'll repost to this forum.Good luck..."

My latest update (from http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/dbdf9e52-8eb9-4a4f-a10e-2764dc20596d ): "I think I've found MY problem; not too sure wheher it's going to be the same for you. In my case, some drives were randomly going into write-protect, and running CHKDSK was one way out of the problem, but only temporarily. On some occasions the CHKDSK would end quickly without any message(s), sometimes it would fail with 'An unspecified error occurred (696e647863686b2e dee).' Either way, the write-protect problem usually went away, but it also came back after the next boot, not necessarily on the same drive(s). The drives that were randomly going into write-protect were all connected via a GBB36X ( rebadged JMB36X) controller chip on my GA-P35C-DS3R m/b, with chip driver version 1.17.42.8 (Win 7 couldn't find a later driver). There was a fix at 1.17.43 which seems to address the problem. I think MS should make sure that the driver update can pick up a later driver, and Gigabyte should also do the same ! "R1.17.43WHQL (11/17/08') - Fix the issue that system event log has error #117 in Vista. - Burning disc sometimes failed with some IDE ODDs on some platforms. - Snake TB-400S PMP hotplug failed. - Fix the issue that hard disk becomes write-protected sometimes on the platform equipped with 4GB DRAM ." If you have any flavour of the JMB36X chip, maybe you should try updating your driver from http://www.jmicron.com/Driver.htm If the problem comes back on my system, I'll repost to this forum. Good luck..." I have the same exact problem, except that I only have one brand new hard drive and one operating system, and I have installed and re-installed windows 7 home edition over 6 times, each time, after a day or two, my folders get hijacked, and I have to continuously take owner ship...I didnt pay a couple of hundred of dollars to waist hours, and be late on work because of this...Isnt their a patch? or a solution>>>>well obviously not because my software is all updated. I need this issue fixed,