jaclaz

Yep, I just imagine the situation at corporate parties where the theme will be strangely revolving around "mine is bigger". jaclaz

I am The Finder, there is a reason for that . Thanks , though being born modest (not all over but in spots ): http://www.quotes.net/quote/39361 I would be very happy with just the "living" (for a looong time). jaclaz

Some news from Samsung: http://www.theguardian.com/technology/2015/sep/03/samsung-launches-smartthings-internet-of-things-hub Just a few days after DEFCON 23 and: http://www.pentestpartners.com/blog/hacking-defcon-23s-iot-village-samsung-fridge/ https://www.schneier.com/blog/archives/2015/08/using_samsungs_.html And some more (IMHO preoccupying) news: http://arstechnica.co.uk/security/2015/09/9-baby-monitors-wide-open-to-hacks-that-expose-users-most-private-moments/ https://www.rapid7.com/docs/Hacking-IoT-A-Case-Study-on-Baby-Monitor-Exposures-and-Vulnerabilities.pdf jaclaz

The French way (JFYI): https://phrozensoft.com/2015/09/windows-privacy-tweaker-4 jaclaz

Sure it is a workaround (poor or not being debatable), the "feature" was implemented by the good MS guys "by design", you can sue them if you don't like it . And (still on the workaround) if you want the system to not recreate those files: http://jamesisin.com/a_high-tech_blech/index.php/2010/09/nevermore-be-bothered-by-desktop-ini/ jaclaz

Does this happen because of lack of permission or because any file is "in use"? Maybe you need to further elevate to "TrustedInstaller" to get rid of some of them from the "online" system : http://www.msfn.org/board/topic/155910-taking-back-the-registry-from-trustedinstaller/ http://www.msfn.org/board/topic/162571-running-explorer-as-trustedinstaller/ http://vorck.com/windows/ntauth.html or boot to a PE and see if you can delete the whole stuff when "offline" (and as "System"). jaclaz

System.ini ? Desktop.ini (twice, one for current user and one for the "public" desktop): http://www.7tutorials.com/why-are-there-two-desktopini-files-my-desktop-what-do-they-do Unless you use custom icons for the folder you can delete them. jaclaz

Will this driver work with a xbox 360 wireless controller? XD The idea about "to follow" may include: http://www.msfn.org/board/topic/119841-xbox360-controller-driver-for-win98/page-2#entry1106321 jaclaz

And little by little existing hardware will fail and new machines will come with Windows 10, and you did not seemingly consider in the projection the success that the Surface 4 will have (at least in the perverted minds of MS executives ). At 14" it is entirely new paradigm, a tablet that is actually a (small) table and costs like an actual design table. It is obvious how this will improve readability of contents and allow to use larger Office 3641/2 spreadsheets surely accountants worldwide will rejoice. (and they will have no objections to pay the equivalent weight in gold for the needed flimsy keyboard to punch numbers in it) If I were the mayor in cities where there is a Microsoft Store I would be starting planning for the additional police resources needed to manage the crowds that will gather outside of them on launch date. jaclaz

Ah, the good days of NT 4.00, no need to move stuff nor to reformat... jaclaz

Yep, that's part of the experimenting, though what you removed "sounds" like "OK" you never know how the OS as a whole will behave until you try it. At least in the good ol'times of XP and nlite the "common issue" was people "removing too much" and then asking how to re-add subsystems or functions that were not (seemingly) connected with what was removed. From what I have seen around it seems like that this (the concept of packages and their assembling/removing/etc.) is about the only thing that the good MS guys made "properly" on Windows 10. The actual "ergonomics" of the management through powershell or similar and the complexity of the DISM tool are of course still something that makes no sense whatever IMHO, year after year it seems like they want to separate as much as they can "common users" from "advanced users" or GUI users from command line users , which may even a be a good thing but why making the life of command line users so difficult and *anything* related to .wim or even worse .esd or more generally "custom" or "unattended" installs such a miserable experience? jaclaz

A hopefully rare and never to be repeated (but not so strange) misadventure : https://www.humankode.com/security/how-a-bug-in-visual-studio-2015-exposed-my-source-code-on-github-and-cost-me-6500-in-a-few-hours Alexa+Amazon+VisualStudio+Github (I don't really want to point a finger on any service/company, nor on the poor fellow developer) sounds like a very palatable cocktail for dishonest bitcoin miners. jaclaz

Not a bad guess. Why don't you check loading the hive in a GUI Registry editor in the PE? At first sight, if you mount the SOFTWARE hive to a TEMP hive the path to the "right" key will be: HKLM\TEMP\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce because: HKLM\TEMP\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce should result in the booted windows as: HKLM\SOFTWARE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce (and BTW another reason to use the offline Registry editing) jaclaz

Poor, little thing , rest assured we do care for you , but it is not like your windows cleaning is like #1 priority for anyone but you . Difficult to say. If you want hyper-v functionalities it may, if you don't want them it's a smart move :. As said earlier, it is not something that the "average user" does and there is no real (that I know of) exact list of packages, of their contents and - much more than that - about the interconnectedness of each package with actual functionalities in the OS and with other packages. The link provided to you here: http://www.tenforums.com/software-apps/20583-can-someone-help-install_wim_tweak.html lists quite a few packages together with their correspondence to the OS functionalities (besides using directly powershell instead of instal_wim_tweak). Info is a bit scattered around, as an example for edge: http://www.intowindows.com/how-to-uninstall-remove-edge-browser-from-windows-10/ partly because Windows 10 is still very recent (and a lot of people are courageously attempting to fight against it) and partly because this is the chaotic way usually findings on this kind of things are managed (or non-managed), you need to extensively search for information and then verify it experimentally. Most probably (haven't ever tried it, nor anyhting later than Windows 7 personally) tools *like* NTLite will soon (or maybe already can) take care of these things but cannot really say. jaclaz

Backslashes are a "strange" thing (and particularly when used in a variable and then put in the Registry). Are you sure that running SET Drive returns: Drive=D: and not: Drive=D:\ Or simply try to use: REG ADD HKLM\TEMP\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /v Act /t REG_SZ /d "%Drive%Activate.cmd" /f As a side-side note, personally I would rather use an Offline Registry editor from a PE: http://reboot.pro/topic/11312-offline-registry/ http://erwan.labalec.fr/other/ jaclaz

Well, at the time I posted post #4 above: Posted 31 August 2015 - 09:09 PM I read on that page the bolded parts exactly as I quoted them from the earlier Wayback Machine shapshot and that page WAS titled "Windows 10". That is not "several days ago". Here are (until they last) a couple google cache: http://webcache.googleusercontent.com/search?client=opera&q=cache:t4VUwDLfErcJ:http://www.glass8.eu/win_future.html%2Bhttp://glass8.eu/win_future.html&oe=utf-8&channel=suggest&gws_rd=cr,ssl&hl=it&&ct=clnk http://webcache.googleusercontent.com/search?q=cache:jlkyDS3bQcgJ:http://www.glass8.eu/%2Bhttp://glass8.eu/&client=opera&channel=suggest&hl=it&prmd=ivns&strip=1&vwsrc=0 taken on 31 August 2015 in the evening and I am attaching a screenshot of them, just in case. As said, I may well be totally nuts but I am usually rather accurate when I state something. And again, if there is a page titled "Windows 10" or "Windows 10 TH2" it is IMHO likely that the average user (ignorant or not) who is running Windows 10 (the sheer fact that he/she is running Windows 10 might actually - according to a few people - automatically categorize the user as ignorant BTW) may click on it, whilst the same won't probably happen if the 10 is removed from it. jaclaz

Sure , but the OP has Windows 10 and even if he hadn't read (or understood due to the conflicting info with the other pages) the page of the guide, he should have had a look at the page: http://glass8.eu/win_future.html which was titled "Windows 10 TH2" and now is (IMHO senselessly) renamed to "Windows TH2" and immediately run away, scared by the bold parts. Hence my post with the "unexpectedly" comment, anyone reading it today would come to the conclusion that I was completely crazy or disconnected from facts (and whilst the first may have some grounds , the second can be easily proved false). In a nutshell this thread is about failures : failure by the OP in reading and/or understanding the complexity of the installation and the tool being reserved to "advanced users" ONLY failure by both me and cmdshft in highlighting how some parts of the tool limitations and difficulties are actually not clearly exposed to the public failure by you to receive any of the above criticism/observations and/or provide any mitigation to the problems listed jaclaz

The .iso is a "container" that contains an "install.wim" image which is also a "container" that contains(usually) more than one indexed images. So you can mount the .iso to access the inner .wim container, but then you need to mount one of the images inside this inner container in order to access the contents. As I tried telling you, you need to mount to a folder the actual indexed image that you want to modify. Please try reading again the given link in #2: https://4sysops.com/archives/windows-7-dism-how-to-mount-manage-and-service-wim-images/ The install_wim_tweak is technically speaking a helper to service an image, you need to learn and understands the basics about mounting and servicing the image in order to use it. BUT, follow me please. You want to MODIFY something, this something is in a container (the .wim file) which is inside another container (the .iso file). Now since by definition the .iso is a READ ONLY filesystem, how do you expect that the changes can be written to it? So you need to extract the install.wim from the .iso and save it locally on hard disk (where it will be accessible as Read/Write) and then mount one of the images in the .wim to a folder that you then give as path to install_wim_tweak. And later you will need to recreate the .iso with the modified install.wim (or use the modified install.wim with direct deployment or through some installing tool). jaclaz

Hard to say, I would say a difficulty level between 3 and 7. jaclaz

Well, to be fair, and just for the record, the page (before it was lastly updated): https://web.archive.org/web/20150826221130/http://www.glass8.eu/win_future.html Had some slightly different contents from the current one: http://glass8.eu/win_future.html jaclaz

Sure , that's an essential freedom of choice . And again, yes, sure. and hopefully before or later that goal will be reached. You were tricked into believing that Aeroglass was a "ready" and "good for all" tool, while it isn't or it isn't yet, as said probably a communication error. jaclaz

Open INSTEAD a cmd prompt (by right clicking - as well with Admin credentials - the CMD.EXE ) DO NOT right click on Install_wim_tweak. (of course a command window will open but it will close automatically as soon as the command has done whatever it is supposed to do which in your case, if you provide the path to a mounted .iso will likely be an error, i.e. you will see the window close immediately) You FIRST open a command prompt and THEN navigate to the directory where the tool is and RUN the tool from command line. That's why I provided you a link to this basic part, numbered as 1) in previous post: http://dosprompt.info/basics.asp As a general rule always, but particularly when a batch or command line tool is involved it is smart to NOT use the Desktop nor any other path with spaces in it. As an example make a new folder C:\wimteak and put the file(s) in it, and when you will have opened the command prompt you would type in it: CD /D C:\wimtweak[ENTER] and then from it you will be able to type/run from command line install_wim_tweak.exe[ENTER] If you provide a path which is not the mount point of an install.wim image (see again item #2) in previous post), you will get an error *like*: C:\wimtweak>install_wim_tweak.exe---------------------------------------------------Registry Tweak Tool v1.4.7.0----------------------for Windows 6.x----------------------Created by Michal Wnuowski-------------Concept by Aviv00@msfn / lite8@MDL---------------Modified by Legolash2o-----------------------------------------------------Type path to mounted install.wim :C:\nopathMountPath : "C:\nopath\"Registry file not found, please make sure your mount path is correct!C:\wimtweak>but the cmd window will not close. jaclaz

Probably the missing (initial) points are : 1) are you typing that in a cmd prompt? (and not on the "run" line) Like: http://dosprompt.info/basics.asp 2)is the WIM (actually an indexed image inside the .wim) mounted to a mountpoint? https://4sysops.com/archives/windows-7-dism-how-to-mount-manage-and-service-wim-images/ jaclaz

Yeah, very difficult to find: https://en.wikipedia.org/wiki/Windows_To_Go https://en.wikipedia.org/wiki/Windows_To_Go#Licensing In a nutshell you need an Enterprise license and Software Assurance. On technet (for Windows 8/5.1): https://technet.microsoft.com/en-us/library/jj592680.aspx jaclaz

Well, technically newbies are not allowed to use that tool, you need a special "advanced user" license for it. Now, seriously, doesn't the main related topic: http://www.msfn.org/board/topic/152688-win6x-registry-tweak/ contain what you are looking for? jaclaz