Guillaume

Member
  • Content count

    95
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Guillaume

  1. Done. Check the first page. The only thing I did was to download the source, change .NET version in project properties and build Fantastic, thank you so much!
  2. I thought I'd make a friendly request here for someone to compile the latest version of install_wim_tweak to run on .NET4(.6). This way, one shouldn't have install an entire .NET runtime on Windows 10 in order remove a couple of components.
  3. How's the issue concerning features being re-enabled when loading a session preset with those features were supposed to be selected for removal coming along. Was still present in 1.07. Also, the selection boxes in the Component Removal tab were very quirky when it came to selecting components that were directly related to features.
  4. Quite sure. This was with x64, if that helps. If I built an image with all of the same options WITHOUT cache removal, 3.5 .NET was okay. In this topic I already stated what was going wrong, how to fix it and what would be a proper solution for it (to be implemented in RT7Lite). Just to recapitulate: - Files were being searched for in specific subfolders in the C:\Windows\assembly folder by the .NET app. - The easy way to fix this is to just extract the Windows\assembly folder from a clean .wim and put them back - The cool way is - since you're having duplicate files on your system if you leave all those files in \assembly - to make either hardlinks or softlinks to those files in the places in Windows\assembly as they would normally appear in a full installation. It is very likely that a full Windows installation does that (using hardlinks) anyways in order to save space, I've never checked that, but in case of RT7Lite this would definitely be the best way to save one from compatibility issues and still save space, since the actual file is present only once, but pointed to from several locations.
  5. Correct. bul*****, that's internal to Opera. But how about wireless internet connection/WPA keys?
  6. Live Messenger is working for me. The ones with Green i have disabled or they run manually.Im pretty sure these are not needed for WLM The Orange one could cause problems for WLM if its removed The Red ones i have enabled always Error Reporting is useless, but removing Remote Access Auto Connection Manager and/or Remote Access Connection Manager is a b*tch. So I recommend you don't remove those two. Additionally, I don't know if it's that good of an idea to remove Protected Storage.
  7. It sounds like you have more of a handle on it than I do, but the issue was present in an pre-beta 1.08 and Ben said that he could fix it. He seems to me a man of his word. Well, yeah, I started out doing the symbolic linking myself and it worked out pretty nicely, but since I don't exactly have a list of what is removed it's a bit more work for me than it is for Ben, who knows in advance what is 'missing'. In essence, I think symbolic linking would be an absolute brilliant solution.
  8. I'd still be interested in knowing whether or not you chose the option to remove the winsxs cache. That option borks .Net; I wouldn't be surprised if it also wrecked \assembly. Yeah I did. It was all about the .NET in this case, yeah (UPEK Protector Suite uses .NET 3.0) I was thinking, though: the files that are removed are (primarily at least) files that are normally duplicates present in another folder. So wouldn't it be a great idea to not just remove the duplicates (which obviously breaks stuff), but to substitute them for symbolic links? That'll save the same disk space, but keep the .NET support in tact.
  9. Seems like it's got everything to do with the absence of folders in C:\Windows\assembly: it searches for all kinds of non-existing folders like C:\Windows\assembly\GAC_64\PresentationFramework\3.0.0.0__31bf3856ad364e35. If I create them and symlink to C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\ the program gets started a little bit further each time, but I can't get it to work completely. Does RT7Lite mingle with the Windows\assembly folder? Edit Copying the entire \Windows\assembly folder from a fresh image fixed the problem.
  10. Is there a change between 1.06 and 1.07 that could relate to the fact that suddenly makes it impossible to run UPEK Protector Suite 2009 (with the legacy drivers, not the Windows Biometrics drivers)? In addition to what I removed from the 1.06 install, I removed this in the not-working v1.07 stripped install: IIS-WebServerRole=True TelnetClient=True TelnetServer=True SensrSvc=True sppuinotify=True Manual windows setup=True Recovery=True Any of the applications, save the tray icon UI, simply crashes whenever I try to start it: Event ID 1000 The following information was included with the event: ctlcntrv.exe 5.9.3.6241 4bb09897 KERNELBASE.dll 6.1.7600.16385 4a5bdfe0 e0434f4d 000000000000aa7d Process Monitor: 1788 QueryOpen C:\Windows\System32\MSCOREE.DLL.local NAME NOT FOUND 1788 QueryOpen C:\Program Files\Protector Suite\ctlcntrv.exe.Local NAME NOT FOUND 1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\fusion.localgac NAME NOT FOUND 1788 CreateFile C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\security.config NAME NOT FOUND 1788 CreateFile C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\security.config.cch NAME NOT FOUND 1788 CreateFile C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\enterprisesec.config NAME NOT FOUND 1788 CreateFile C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\enterprisesec.config.cch NAME NOT FOUND 1788 QueryOpen C:\Program Files\Protector Suite\profapi.dll NAME NOT FOUND 1788 CreateFile C:\Users\Guillaume\AppData\Roaming\Microsoft\CLR Security Config\v2.0.50727.312\64bit\security.config PATH NOT FOUND 1788 CreateFile C:\Users\Guillaume\AppData\Roaming\Microsoft\CLR Security Config\v2.0.50727.312\64bit\security.config.cch PATH NOT FOUND 1788 QueryDirectory C:\Windows\assembly\GAC_64\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.INI NO SUCH FILE 1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ole32.dll NAME NOT FOUND 1788 QueryOpen C:\Program Files\Protector Suite\CRYPTBASE.dll NAME NOT FOUND 1788 QueryDirectory C:\Program Files\Protector Suite\ctlcntrv.INI NO SUCH FILE 1788 QueryOpen C:\Windows\assembly\GAC\PublisherPolicy.tme NAME NOT FOUND 1788 QueryOpen C:\Windows\assembly\NativeImages_v2.0.50727_64\WindowsBase\385daef1d59c01201d35cdd277f99a56\WindowsBase.ni.dll PATH NOT FOUND 1788 QueryOpen C:\Windows\assembly\GAC_64\PresentationFramework\3.0.0.0__31bf3856ad364e35 PATH NOT FOUND 1788 QueryOpen C:\Windows\assembly\GAC_MSIL\PresentationFramework\3.0.0.0__31bf3856ad364e35 PATH NOT FOUND 1788 QueryOpen C:\Windows\assembly\GAC\PresentationFramework\3.0.0.0__31bf3856ad364e35 PATH NOT FOUND 1788 QueryOpen C:\Program Files\Protector Suite\PresentationFramework.dll NAME NOT FOUND 1788 QueryOpen C:\Program Files\Protector Suite\PresentationFramework\PresentationFramework.dll PATH NOT FOUND 1788 QueryOpen C:\Program Files\Protector Suite\PresentationFramework.exe NAME NOT FOUND 1788 QueryOpen C:\Program Files\Protector Suite\PresentationFramework\PresentationFramework.exe PATH NOT FOUND 1788 QueryOpen C:\Program Files\Protector Suite\ctlcntrv.exe.Local NAME NOT FOUND 1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\en-US\mscorrc.dll PATH NOT FOUND 1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\en-US\mscorrc.dll.DLL PATH NOT FOUND 1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\en\mscorrc.dll PATH NOT FOUND 1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\en\mscorrc.dll.DLL PATH NOT FOUND 1788 QueryOpen C:\Windows\Globalization\en-us.nlp NAME NOT FOUND 1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\VERSION.dll NAME NOT FOUND 1788 QueryOpen C:\Program Files\Protector Suite\VERSION.dll NAME NOT FOUND
  11. That's not good, I think you can cancel it and start again Then again, that'll mean you will have to select all the components and configure all the settings again, since RT7Lite doesn't save the .inf before, but after the process... I'd rather see that fixed and the inclusion of a log file if the problem of components not being removed persists. That'll save a lot of work if something happens to go wrong during the process. There you go, didn't read that in time +1
  12. I concur. Pity, the removal components process still gives me some gripes. I've tried to get rid of WMP and Games just to name a few but to no avail. Didn't try to remove WMP (would that work without the loss of WMV support within browsers?) Games can be removed without a problem. If they're not removed, then you have the same problem as I described earlier: most of the times the removal process leaves a couple of components untouched, even though they were selected for removal. Really strange. Not when you know what you're doing. I've been running systems without any antivirus/antispyware software installed for years now, just know your sources well. That shouldn't be the case. For as much as I know, apart from the 'Help' and 'Default Programs' in the Start menu which remain after component removal, most other shortcuts (I think you meant shortcuts, rather than icons?) are nicely removed together with the components. When a feature is ENABLED in the features pane on the right, then it's grayed in the component removal pane, as it cannot be removed. If a component is selected for removal, then the corresponding feature is grayed on the right. This should be intuitive, but as of yet it is extremely buggy, possibly causing or being part of the problem with components not being removed. +1 Why would you run a double firewall setup? I'm aware of the UAC option within RT7Lite, yeah, but I'd rather have it removed. I was just wondering if my observations with its removal could be verified.
  13. My personal opinion is that UAC is extremely annoying if one knows exactly what he's doing, hence I want it removed. Even though UAC is less prominent in W7 compared to Vista, I think lots of people will want to remove it as well, although for the wrong reasons (the bad reputation UAC has given itself with Vista). Hence its removal being an extra security risk because of an unadvertised change in the default credentials should be investigated. Third, I'm an absolute minimalist: whatever I don't absolutely need and can remove, will be removed. This goes all the way to stripped drivers etc.
  14. Say what? Correct, so... what's your point?
  15. Yipes! By removing User Account Control, it seems that the Guest account and other restricted/standard/non-admin accounts gets all kinds of user privileges: I can uninstall *some* software, I can register .dll files. Can anyone confirm this?