The other day I booted Windows 7 beta 7100 and chkdsk ran for the first time since installing Win7 last April. chkdsk found dozens and dozens of problems with the file system, but eventually successfully booted Win7. However it caused number of problems. These two have been the most problematic: 1) Many file associations have been lost and can't be set manually anymore. 2) All of the Microsoft Management Console (Mmc.exe) snapins don't work anymore. File associations: Many file associations I've set manually have been lost. And something related to the process has been seriously corrupted. Neither of two methods of setting them work anymore. When I right-click on a file, select 'Open With' and choose 'Choose default program', an 'Open with' window pops up. But when I browse to the executable I want to open the file and select it, it doesn't end up being added to the 'Open with' anymore like it is supposed to. I have the same problem if I access the settings through, 'Control Panel' > Programs > Default Programs > 'make a file type always open in a specific program'. Microsoft Management Console: After the system ran chkdsk and found dozens of problems with th file system at boot, I immediately tried to access the chkdsk log in 'Event Viewer', but got this popup MMC error message: "mmc has detected an error in a snap-in and will unload it" Closing the popup, this was the error message in the console: "mmc could not create the snap-in. The snap-in might not have been successfully installed correctly. Name Event Viewer "clsid:fx:[b05566ad-fe9c-4363-be05-7a4cbb7cb510}" Besides the 'Event Viewer' problem, it seems all the other MMC related snapins are experiencing the same basic problem. Many hours of googling came up with a possibility of problems with the Microsoft .NET Framework installation. But I've yet to get a handle on the complexities involved with the many different versions of .NET Framework, and how they might be related to this problem. Another approach was to run the System File Checker command: 'sfc /scannow'. But that process stalled after 5-10 minutes at the 25% point. I've left it run like that for a good two hours a few times. But the process never completes, and the system slows radically with the time to execute a single mouse click taking up to 2-10 minutes. There were two components I added to the OS recently that I suspect may have caused the initial file system problems. 1) The new Windows 7 compliant ZoneAlarm Antivirus 9.0 Beta. 2) The latest Windows 7 nvidia7300 SE / 7200 GS drivers. I didn't notice any problems with Win7 after installing ZoneAlarm. But the file system corruption that forced a chkdsk scan at boot happened only 1-2 days after installing it. And the only error message that continually popped up booting into Windows after the system initially ran that chkdsk scan, was one related to ZoneAlarm. I've since uninstalled it. In the past few months I have seen problems with both of the two different versions of Win7 compliant nvidia drivers I've installed. While multitasking during video playback, I've had the screen go black for up to 10-25 seconds at a time. After the monitor display came back I've gotten a message saying the video driver had just successfully recovered from a crash. Any thoughtson all this would be greatly appreciated. ThxTS

I just managed to run sfc /scannow from a command prompt in safe mode to try to find outexactly what was corrupted in my copy of Win7, and possibly have things repaired. It concluded with a message saying it found several corrupted files, but was not able to repair them. sfc.exe created an enormous 5611 KB error log file, but it's way beyond my abilities to decipher.Any chance someone out there could take a look at the file and help mework outsome of theproblems it found?I was going to upload the sfc cbs.log file to my old Yahoo/GeoCities web space and create a link to it.But they've recently shutdown all of the old free web space people have been using for years. With all the very long lines of text in the file, pastingit allhere would probably look very confused.Again, any thoughts on working this all out would be greating appreciated.ThxTS

Try using system restore to an earlier point. If you have no restore points you can performe a repairupgrade similar to upgrading from vista which keeps your files and programs but instead from windows 7 to windows 7. This may repair the files and entries that SFC was not able to.

You might have to do an upgrade-in-place or a repair install.To upgrade-in-place, insert your Windows 7 RC DVD and select "install now". Note, you can "upgrade" to the same version.To repair, boot your DVD and select "repair my computer".You could upload your log files to SkyDrive. Log in with your Windows Live ID.

Thanks folks.My first attempt at fixing things was to restore an earlier restore point. But I'd been having problems with that too in the past few months. For some reason only one, the most recent point, was being set every time something new was installed. I thought I'd addressed it, but when this issue 1st popped up, there was still only the most recent restore point available. That was set by a windows update installed the same day this issue popped up.I'm not really ready to do a complete reinstall/'repairupgrade.' That approachseemsa bit too radical at this point, at least from my limited experiences doing that in the past.Also, booting the Win7 installation DVD and selecting 'repair' at the 1st options window only presents a list of options that doesn't seem to include any kind of repair option that would address corrupted OS files. There's an option there to repair startup/boot issues. I've used that in the past succesfully. But it doesn't address the kinds of problems I'm seeing now.I've uploaded (thx for the link) the CBS.log file (5611 KB) thatsfc.exe created here:http://cid-2f2de919606708e0.skydrive.live.com/self.aspx/.Public/CBS.logThere's a bunch of machine code in it just below the line:2009-09-01 13:19:36, Info CBS Manifest parsing error at line: 1, context:It would only save as unicode when I was trying to upload the file elsewhere. Don't know if it represents anything significant.It's a huge file, and quite mind-rattling from my perspective... 8-OThxTS

Thanks for the info.Unfortunately I don't think I can make any sense out of the CBS.log either.Hopefully, someone else will answer.

Meanwhile... I wonder if someone might have a suggestion on whyI can'tassociate file types (see original post above)anymore. I'm going nuts not having Media Player Classic pop up automatically when I watch videos. I have a graphics viewer I like to use too that has lost file association.I've exhausted my googling efforts trying to find a solution at this point.ThxTS

You can use this command to view the [sr] entries in the cbs log: findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txtA text file will be appear on your desktop.You can move or delete the cbs log and re-run the sfc scan to shrink the log size and narrow your search.

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.tx ?????? ... What does that get me? I just open the whole file in Notepad. I can search for text pretty easily that way if I know what I'm looking for. I've saved a copy ofthe log file in another location for reference.

This makes a text file of all the sfc.exe operations [sr] and excludes other such as your windows update errors from the cbs log.

This makes a text file of all the sfc.exe operations [sr]... Searching forsomething to explainwhat you were talking about there lead me to a Microsoft webpage talking about how to analyze the sfc.exe log file entries. Searching the cbs.log filefor the string "Cannot repair member file" described there, I was able to determine the corrupted files that sfc found, but couldn't repair: Cannot repair member file [l:18{9}]"audit.exe" Cannot repair member file [l:30{15}]"BdeHdCfgLib.dll"Cannot repair member file [l:24{12}]"calc.exe.mui"Cannot repair member file [l:18{9}]"dfdts.dll"Cannot repair member file [l:16{8}]"drmk.sys" of wdmaudio.infCannot repair member file [l:22{11}]"HdAudio.sys" of hdaudio.infCannot repair member file [l:34{17}]"I386\GS1403E3.PPD" Cannot repair member file [l:16{8}]"img4.jpg" Cannot repair member file [l:16{8}]"img5.jpg"Cannot repair member file [l:16{8}]"img6.jpg"Cannot repair member file [l:18{9}]"img10.jpg"Cannot repair member file [l:18{9}]"img11.jpg"Cannot repair member file [l:18{9}]"img12.jpg"Cannot repair member file [l:18{9}]"img16.jpg"Cannot repair member file [l:18{9}]"img29.jpg"Cannot repair member file [l:18{9}]"img28.jpg"Cannot repair member file [l:18{9}]"img30.jpg"Cannot repair member file [l:48{24}]"InputPersonalization.exe" Cannot repair member file [l:32{16}]"kernel32.dll.mui"Cannot repair member file [l:28{14}]"mfplat.dll.mui"Cannot repair member file [l:34{17}]"MIGUIControls.dll"Cannot repair member file [l:14{7}]"mip.exe" Cannot repair member file [l:32{16}]"mmcndmgr.dll.mui"Cannot repair member file [l:18{9}]"mraut.dll" Cannot repair member file [l:26{13}]"mshwLatin.dll" Cannot repair member file [l:24{12}]"msoobeui.dll"Cannot repair member file [l:24{12}]"msra.exe.mui"Cannot repair member file [l:22{11}]"msvcm80.dll" Cannot repair member file [l:32{16}]"netevent.dll.mui"Cannot repair member file [l:22{11}]"NetProj.exe"Cannot repair member file [l:32{16}]"nettrace.dll.mui"Cannot repair member file [l:26{13}]"ntdll.dll.mui"Cannot repair member file [l:18{9}]"ntevt.dll" Cannot repair member file [l:28{14}]"OmdProject.dll"Cannot repair member file [l:22{11}]"oobeldr.exe"Cannot repair member file [l:22{11}]"portcls.sys" Cannot repair member file [l:40{20}]"PresentationCore.dll" Cannot repair member file [l:44{22}]"PrintBrmEngine.exe.mui"Cannot repair member file [l:22{11}]"rdpendp.dll" Cannot repair member file [l:32{16}]"sdengin2.dll.mui"Cannot repair member file [l:32{16}]"sdiageng.dll.mui"Cannot repair member file [l:32{16}]"SnippingTool.exe"Cannot repair member file [l:22{11}]"rdpendp.dll" Cannot repair member file [l:24{12}]"tscfgwmi.dll" Cannot repair member file [l:20{10}]"US-wp4.jpg"Cannot repair member file [l:20{10}]"US-wp6.jpg"Cannot repair member file [l:32{16}]"winsetup.dll.mui"Cannot repair member file [l:32{16}]"wsecedit.dll.mui"Cannot repair member file [l:30{15}]"mstscax.dll.mui" Cannot repair member file [l:32{16}]"UIRibbon.dll.mui" Cannot repair member file [l:32{16}]"UNIDRVUI.DLL.mui" Cannot repair member file [l:20{10}]"wzcdlg.dll" Cannot repair member file [l:26{13}]"Wwanadvui.dll" Cannot repair member file [l:24{12}]"xwizards.dll" To no surprise it shows problems with the Microsoft Management Console file: mmcndmgr.dll.muiIt also explains why Win7's calculator, calc.exe.mui, isn't workingNow I need to figure out what I was doing wrong thatmade sfc.exeunable to restore them.Back in the Win98days sfc would prompt me to insert the Windows installation disk. Don't know if it works the same in Win7. I ran sfc from a command prompt in Win7's Safe Mode because it kept stalling booted to Win7 normally.I also tried running sfc from a command prompt after booting the Win7 installation, and selecting the command prompt option from the repair menu. But it stalled there too.Must be some way to restore those files.TS

I see that mmcndmgr.dll.mui is a simple51 KB ascii configfile. But the cbs.log reports that the backup file that sfc uses to replacethedamagedfile is also corrupted.Both corrupted:C:\Windows\System32\en-US\mmcndmgr.dll.mui C:\Windows\winsxs\x86_microsoft-windows-m..demanager.resources_31bf3856ad364e35_6.1.7100.0_en-us_7a4b259bc72ef8aa\mmcndmgr.dll.mui I wonder if someonecould compare their working copy to mine:http://cid-2f2de919606708e0.skydrive.live.com/self.aspx/.Public/mmcndmgr.dll.muiIf it's not a file customized for each installation, maybe someone else's copy might work for me.Here's a copy of the file that opens as a web page:http://www.geocities.com/taku_skan/mmcndmgr.dll.mui.txtTS

This may be a bitinvolvedbut a way to get these files quicklyis tomake your own backup cacheby keeping an expanded image of the "install.wim" file found on theDVD in the sources folder on you hard drive. If you have enough disk space (40GB) you can extract all of the windows 7 system files to disk with a file archivetool such as 7zip, then deleteall the numbered folders that are not your installed version.---------------------------Anyway, I downloaded the file and tried to examine it's resources and the messege given was "this is not a valid win 32 executable file" which could mean it's corrupt or it's a 64 bit file from a 64 bit operating system.

Here is a link linkto that .mui file from my system. Version 7100 32 bithttp://hzl5oq.bay.livefilestore.com/y1pIrIti6RtnuGntPJPZ3hTRhn_YhiAJypw-KET1mR7TCwI60_Vx16ysDfLrK9I2_wA5-Foi7AYXuQZ3GJNsKuyrygtuGzqveym/mmcndmgr.dll.mui?download

Anyway, I downloaded the file and tried to examine it's resources and the messege given was "this is not a valid win 32 executable file" which could mean it's corrupt or it's a 64 bit file from a 64 bit operating system.Here is a link linkto that .mui file from my system. Version 7100 32 bit... When you say, "I downloaded the file and tried to examine it's resources," are you referring to install.wim or mmcndmgr.dll.mui? I assume you mean mmcndmgr.dll.mui.Ifyou're referring to mmcndmgr.dll.mui,then it doesn't appear you selected the right one for the Windows 7 Version 7100 32 bit OSwe both apparentlyhave. At least not one that's the same as the file I have on my system. There's nothing at all within your file I downloaded that matches anything in mine.For instance, there are a number of references to 'Channel uid' in mine that looks like XML code. There's no text string matching thatanywhere in your file.It also appears that yours is a binary file with machine code from the characters I see at the beginning of the file. Did you compare the mmcndmgr.dll.mui you extracted from install.wim to the one in your existing Win7 installation? The size, 51 KB matches mine. But that's about all.In fact, I did manage to figure out how to extract files from install.wim the other night using freeware called Universal Extractor. But I found no install.wim file among the extracted files.However, you say install.wim should extract files that total in size to around 40 GB. If that's true, then that means Universal Extractor probably aborted its extraction process when the drive it was extracting to filled up. The numbers I'm adding up seem to support that. I'll try freeing up >40GB file space on that drive and try again.ThxTS

I'll keep it simple. I examined the mmcndmgr.dll.mui file downloadedfrom your sky drive and it appears to be corrupt.I tried to load your file into a resource editor and it gave me an error. Mine loaded in fine. I compared it to a file with the same name and data size. I did not examine this file with a text editor.

In fact, I did manage to figure out how to extract files from install.wim the other night using freeware called Universal Extractor. But I found no install.wim file among the extracted files. ImageX, from the Windows AIK can mount a WIM.You can also extract using IsoBuster or 7zip, and probably plenty of other compressed file utilities.One wonders why explorer doesn't have support for it the way it does for ZIP files.

> ImageX, from the Windows AIK can mount a WIM.> You can also extract using IsoBuster or 7zip, and probably plenty of other compressed file utilities.To make a backup cache I tried mounting it with imagex and unzipping with 7zip. It works but when it's mounted to a directory I believe it is still in a compressed state so it takes a long time to copy it from the mount folder to another location. Also copying from the mount foldergives filepermission errors soI just 7zip extract it, that is if I have the disk space. There is a manifest .xml file there in the root with the image index telling which numbered folder goes to which version of windows so I know what ones to delete. > One wonders why explorer doesn't have support for it the way it does for ZIP files.The wim file is probably designed to be mounted and extracted bydeployment professionals and so an inexperienced usercan not easily tamper with it causing system failures. Also the .wim file is designed to be successfully extractedwithout there being a loaded operating system. For example boot.wim extracts during the begining phase of setup before explorer.exeexists on the hard drive.

The wim file is probably designed to be mounted and extracted bydeployment professionals and so an inexperienced usercan not easily tamper with it causing system failures. Also the .wim file is designed to be successfully extractedwithout there being a loaded operating system. For example boot.wim extracts during the begining phase of setup before explorer.exeexists on the hard drive. Still, it would be nice to be able to enable it somehow.Another complication is that a WIM can have multiple images within it. 7zip shows them as separate folders whereas ImageXrequires you tochooseone to mount.

True. There is an xml manifest file in the root of the expanded wim and has the corresponding versions butit may behard to read if your not familiar with it. It's the same file that displays on the command line with imagx info infriendly format. Both methods take about the same time.The only confor imagexispermission file problems and possibility of imagex process crash and having afamiliaritywith this command line tool. Imagex may not work properly on windows 7 as a techniciancomputer with the error: "interface unknown".Unzipping works as long as you don't delete the wrong folder and have adequate disk space so there are several factors which woulddetermine howone would go about the operation.

TakuSan wrote: In fact, I did manage to figure out how to extract files from install.wim the other night using freeware called Universal Extractor. But I found no install.wim file among the extracted files. Whoops... That shound read, "But I found no>>mmcndmgr.dll.mui<< file among the extracted files." I guess you guys figured that out.Brian Borg wrote: ImageX, from the Windows AIK can mount a WIM.You can also extract using IsoBuster or 7zip, and probably plenty of other compressed file utilities I found a copy of Win7 compatible AIK and was downloading for that reason. But while it was downloading I found that free Universal Extractor utility that seemed a lot less to have to deal with just to extract the files from install.wim.TS

Mr. Seven wrote: I tried to load your file into a resource editor and it gave me an error. Mine loaded in fine. I compared it to a file with the same name and data size. I did not examine this file with a text editor. You say, "Mine loaded in fine. I compared it to a file with the same name and data size."Are you saying that you compared the copy of mmcndmgr.dll.mui that you extracted from install.wim to the copy inyour Win7 %windir%\System32\en-US ?Just matching the name and size won't tell you if two files are identical. You need a utility that compares the basic bits of one file to another in order to get an accurate comparison. I use something called Beyond Compare, but there are many probably a lot better.But that's why I'm wondering if the copy of mmcndmgr.dll.mui you extracted from install.wim is the right one to match the one in your Win7 Version 7100 32 bitinstallation. As I said, nothing in mine matches anything in the one you posted online.If the copy you put online IS in fact the one I'm supposed to have, I'm srcxxxd. I downloaded and renamed it properly... changed ownership of my existing copy and set full privileges so I could rename and disable it... dropped yours in next to it, and rebooted my system. Launching Event Viewer got the same initial error popup I got before, but on closing that, I get another now that's new:=====================e module was expected to contain an assembly manifest. (Exception from HRESULT: 0x80131018)at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Activator.CreateInstance(String assemblyName, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark) at System.Activator.CreateInstance(String assemblyName, String typeName) at System.AppDomain.CreateInstance(String assemblyName, String typeName) at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName) at Microsoft.ManagementConsole.Internal.SnapInClient.CreateSnapIn(String assemblyName, String typeName) at Microsoft.ManagementConsole.Internal.ClassLibraryServices.Microsoft.ManagementConsole.Internal.IClassLibraryServices.CreateSnapIn(String assemblyName, String typeName) at Microsoft.ManagementConsole.Executive.SnapInInitializationOperation.OnStart() at Microsoft.ManagementConsole.Executive.Operation.Start() at Microsoft.ManagementConsole.Executive.RunningOperationsTable.EnqueueOperation(Operation operation) at Microsoft.ManagementConsole.Executive.StandAloneComponentData..ctor(SnapInRegistrationInfo info, Int32 bookkeepingId) at Microsoft.ManagementConsole.Advanced.FrameworkSnapInFactory.Microsoft.ManagementConsole.Advanced.ISnapInFactory.CreateSnapIn(Int32 bookkeepingId, String snapInKey, Object& snapIn)========================There may bemore problems related to launching MMC than just that one file.And why is the name of the file you extracted so wierd?: y1puE3u2MyYyIiq-RqUiYEexumsRhvjACE-fTnSSHeHa-_QdQzxdWVZqhKXgBqH78khjx3ogJLMpZFk_fC7_XD21wWhere did that come from??TS

What I'm getting at is that file from your sky drive is corrupt. When I load it to note pad I get an xml style layout. What I should see if it was a real .mui file is undecipherable machine code.That file I gave you was not extracted rather taken from my windows 7systemI'm currently using from c:\windows\system32\en-us. The url to the file I gave you is a direct download link to my skydrive folder. Those links are not normally used for direct downloads but for public sharing, that's why the link is not a "friendly" URL.

True. There is an xml manifest file in the root of the expanded wim and has the corresponding versions butit may behard to read if your not familiar with it. How difficult/easy is it to find the specific copy of mmcndmgr.dll.muiyou're looking for with install.wim opened in7zip? Does that xml manifest file give you any idea of where mmcndmgr.dll.muiis locatedin the display 7zip presents? I know it's not all that easy to locate a specific file in WinRAR's display when you use it load an enormous archive.But that method would save me the trouble of clearing out 40 GB free space to extract everything in install.wim with Universal Extractor.TS

You could use the mmcndmgr.dll.muifrom my sky drive but your system is corrupt according to the sc log so there would be too many files to replace from what I saw.Your best bet right now is to get your 7 dvd insert it into the opticaldvd drive and do an inplace upgrade. Justas if you were upgrading fro vista to 7 - same thing. Thisshould repair and replace mostof your system files with newones. As for the install.wim file: "This may be a bitinvolvedbut a way to get these files quicklyis tomake your own backup cacheby keeping an expanded image of the "install.wim""I was just mentioning how i keep a backup of my system files but I probably shouldn't have....After you repair/upgrade your systemyou should have more time to get aquanted with wim files because it's rather involved.

You could use the mmcndmgr.dll.muifrom my sky drive... Yeah... as I said, I tried that with no success. ... but your system is corrupt according to the sc log so there would be too many files to replace from what I saw. It turns out that the majority of entries in that sfc generated cbs.lof file were dated from before the day the problem started and I ran sfc manually. I guess the system runs sfc on its own from time to time. When I examined the entries for the date I ran sfc manually, I found sfc had checked the same files 3-4-5 times. When the duplicate attempts were eliminated, it turned outonly the ones in the list I posted above had problems. If I subtract the jpg files, that leaves me with 42 files sfc reported as corrupt. ... Your best bet right now is to get your 7 dvd insert it into the opticaldvd drive and do an inplace upgrade. Justas if you were upgrading fro vista to 7 - same thing. Thisshould repair and replace mostof your system files with newones Seems that's the logical way to go at this point. But this is kind of a good learning experience. It's a bit of a challenge at this point to see if just restoring files might actually have a chance of fixing most problems. I've got plenty of time on my hands.I may try extracting just the files for Win7 Version 7100 32 bit from install.wim with 7zip if I can make any sense out of that xml manifest file you mentioned. And then do a file search for each of my corrupted files.My mistake onthat comment I made above on your comparing files. I read what you wrote wrong. You wrote, "I did not examine this file with a text editor." And for some reason my mind blanked out the "not" in that sentence.TS

I've been replacing corrupted files from install.wim after determining that its folder #5 contains the files for Windows 7 Ultimate.I was able to change the permissions on 99% of the corruptedfiles so I could rename/disable them, and restoreworking copiesfrom istall.wim. But when I came to MIGUIControls.dll I found that even after successfully changing the permissions for the file, I still got an error messagerefusing to let meto rename/disable it.Googling ... MIGUIControls.dll ...I found a Microsoft Vista support page that saysit's related to the Even Viewer:http://support.microsoft.com/default.aspx/kb/937630That'sone of the first utilites I found wasn't working for me in Win7.I had the same problem with: drmk.sys portcls.sys msvcm80.dll GS1403E3.PPD HdAudio.sysCan someone tell me if there's a special process for modifying these files? Meanwhile I'll try from safe mode.ThxTS

Some files can not be renamed if they are in use and you find this for .sys driver files. You may have to modify/rename these files offline (from another loaded operating system while the malfunctioning one is not in use). However some of those files you may be able to modify if you do a clean boot and by clean boot using sytem configuration to disable all stertup programs and to load the basic required drivers and only to start microsoft services by disabling third party services.

Some files can not be renamed if they are in use and you find this for .sys driver files. You may have to modify/rename these files offline (from another loaded operating system while the malfunctioning one is not in use). I dual-boot Vista and Win7. But it seems Vista is aware of Win7.In the dual-booting process, they seem interlinked to some degree. Booted into Vista, I still got the same error message refusing to rename that MIGUIControls.dll that lives on another drive with Win7. However some of those files you may be able to modify if you do a clean boot and by clean boot using sytem configuration to disable all stertup programs and to load the basic required drivers and only to start microsoft services by disabling third party services. I'm not familiar with any procedure like that other than botting into safe mode. I tried that but didn't have any success renaming the file.Maybe this is the time to go back and figure out how to set a flash (thumb) drive to boot into something that enables NTFS file processing abilites. I was able to set up a flash drive that boots into MS-DOS using and old floppy disk image. But that leaves me booting into a FAT file system where access to NTFS formatted drives can't be accessed.Maybe there's a Linux image fora flash drive available somewhere.TS

From the vista desktop there is no real reason you should not be able to have the ability tofully modify files that is rename, move even deleteif you take ownership and grant youself permision to manipulate those files.

Well... Does that apply tosystem where Vista and Win7 are installed to dual boot from the same hard drive?I bootedintoVista, browsed to the file on the Win7 drive in Windows Explorer, and it refused to be renamed.I changed the ownership and permissions to one for the Vista administrators. But the darned file still refused to be renamed.Reason ... ??? Maybe it's because the file is currupt in some way different from most of the other files I disabled succefully??TS

I neverhad a problem with it. Are you adding inheritible permissins with the check boxes at the lower right of the diologue in the advanced tab?

I saw an two entries for Adminstrators at one point. One for Adminstrators, and one for Adminstrators withinheritible permissions At that point I'd forgotten (and didn't see what is front of me where you pointed) about theinheritible permissions setting.So both in Win7 and in Vista, I set ownership for the username I was logged in as which didn't appear in those menus as having another entry withinheritible permissions. But even like that I couldn't rename the file.I tried the same in Vista by setting SYSTEM as owner with full permissions. Still no luck.I just deleted all entried allinheritible permissions in Win7 where I am now, but still no joy.What's wacky is that when logged into my user account with administrator privileges, and with the darned file set with Administrators ownership and full privileges, if I try to rename the file, the error message says: "You need permission fromAdministrators to make changes to this file."TS

The current user should be the owner and grant maximum permission to all groups. You may have to add a user in advanced.http://support.microsoft.com/default.aspx/kb/308419

I'm the only user on this (Win7) system. So my choices for, "User, Group, or Built-in security principal" are just: <MyUsername> Administrators SystemPretty much ditto in VistaDid you catch this above ^?: What's wacky is that when logged into my user account with administrator privileges, and with the darned file set with Administrators ownership and full privileges, if I try to rename the file, the error message says: "You need permission fromAdministrators to make changes to this file."I get that both in Win7 and Vista.TS

The fix for the permission problem I had was terribly simple. The system wouldn't let me rename certaiin files because the permission for the folderscontaining themwouldn't allow it. Changing the folder permissions solved the problem. In the process I managed to replace the corrupted MIGUIControls.dll file (in super hidden \windows\assembly subfolder) which got the Event Viewer and Computer Management utlities working again.But now can someone tell me how to change permissions for the \Windows folder and all subfolders and files?I thought I'd mastered Windows permissions at one point. But setting Windows permissions recursively seems to require something I haven't picked up, if possible at all. My method doesn't get me full control over all files and folders.Here's what I've tried from my user account with full Administrator privileges:Change File and Folder Ownership:1Right click \Windows, select Properties2Security tab > Advanced > Owner3Edit > Change 'Trusted Installer' to Administrators4Tick the box that says, "Replace owner on subcontainers and objects" and click OK5Wait while ownership changes are set6Click OK on the security warning, click OK to 2 more windows to exit.Change File and Folder Permissions:7Right click \Windows, select Properties8Security tab > Advanced > Permissions tab9Click 'Change Permissions'10Select Adminstrators11Click Edit12Tick 'Full control'/Allow box13From "Apply to' menu, select "This folder, subfolders and files14Click OK, and OK on the window below, click YES to security warning15Wait while permissions are changed16 Click OK to the Advanced menu, and OK to the Properties menu.On step 5 the system took a few minutes to set ownership of all files and folders. But on step 15, the process took only a few seconds, and I only was a handful of file names flash by.When Icheck permissions ona file like: C:\Windows\System32\en-US\acppage.dll.muiI findthat there full permissions were >not< set for Administrators. I found most permissions on most files, including write and delete permissionsto be disabled.The same for most folders. For example: C:\Windows\System32\en-US\Licenses Although it appears theownership ofall files and folderswas changed toAdministrators, most files and folders haven't been set for full permissions for the Administrators.I'm sure Microsoft has made changing these settings to be a non-trivial task for security reasons.Does anyone know if there's a relatively quick method to mass-change all these permissions. It would make my work replacing corrupted files a >lot< easier.ThxTS

It is preferable if the current user is an administator, that the current user be the file-folder owner rather than theadminisrators group. If the current user is an administrator that user willhave more control over the files and folders by being the sole owner and not sharing ownership with other administrators."Please remember to vote if you find a post to be informative."

That may be. But if I repeat the procedure I outlined about, and instead of configuring the permissions for Administrators, I set them for my personal user account... the results are the same. Full permissions are >not< set for the user account recursively.TS

There are check boxes at the lower right of the advanced permissins tab you must also select for example one of them says for a single file "include inheritable permissions from this object's parent".

There are check boxes at the lower right of the advanced permissins tab you must also select for example one of them says for a single file "include inheritable permissions from this object's parent". And what does that do?

There are check boxes at the lower right of the advanced permissins tab you must also select for example one of them says for a single file "include inheritable permissions from this object's parent". And what does that do? If you clear the checkbox for "include inheritable . . .", you are blocking the permissions of the parent folder. In this case Windows asks if you want to copy the permissions from the parent folder. I always do. If I need to change ownership I do that first. Then I select which permissions I want to block or add from the permissions copied from the parent.