alacran

I like Asimov's books but I haven't read that one. First time you posted that Iink I din't check it. This time I follow the link and now know what you mean.

@ JorgeA Yes, you are right and I am wrong. It was very badly written for a a guy that wanted to make more impact to the mind using 3000% (which sound as very big number) and then he created a non sense. As you may already note English is not my mother tongue, what happened to me is that the only possible way to make it have sense is taking it as 1/(3000%) = 1/30 and when I read it my mind just take it that way, ignoring the meaning of each single word. Because LITERALY he is saying: 100% - 3000% = (100/100) - (3000/100) = 1 - 30 = - 29 (negative time) which means you get the info before it has been send, (Great invention TIME MACHINE).

I understand Shortening by = dividing by, I should not have made any mention of decreasing wich is minus something. My mistake. The mathematical expression is OK my poor English not. The question Was about shortening by 3000 % 3000 % = 30000/100 = 30 3000/100 = 30 (Edited I had extra zero) So shortening by 3000 % = 1/30 of initial quantity or 0.03333x So if initial quantity is 100 then 100/30 = 3.333 or 100 x 0.03333 = 3.333 Edit: Typo

Windows Updates Can be Intercepted to Inject Malware into Corporate Networks If you think that the patches delivered through Windows update can not be laced with malware, think again. Security researchers have shown that Hackers could intercept Windows Update to deliver and inject malware in organizations. Security researchers from UK-based security firm ‘Context’ have discovered a way to exploit insecurely configured implementations of Windows Server Update Services (WSUS) for an enterprise. What is WSUS in Windows? Windows Server Update Services (WSUS) allows an administrator to deploy the Windows software update to servers and desktops throughout the organization. These updates come from the WSUS server and not Windows server. Once the updates are with the administrator on the server, he can limit the privilege for the clients in a corporate environment to download and install these updates. As the admin is the owner of the distribution of these updates. Intercepting WSUS to Inject Malware into Corporate Networks By default, WSUS does not use SSL encrypted HTTPS delivery for the SOAP (Simple Object Access Protocol) XML web service. Instead, it uses the non-encrypted HTTP. This is a major WSUS weakness that should not be ignored now. (At least when it has been exploited and shown to the world). As WSUS installations are not configured to use SSL security mechanism, hence they are vulnerable to man-in-the-middle (MitM) attacks. According to researchers Paul Stone and Alex Chapman, the attack is so simple that a hacker with low privileges can set up fake updates that can be installed automatically by connected machines. All update packages that are downloaded from the Microsoft Update website are signed with a Microsoft signature. Which cannot be altered. However, Hackers can alter Windows Update by installing malware in the metadata of the update. "By repurposing existing Microsoft-signed binaries, we were able to demonstrate that an attacker can inject malicious updates to execute arbitrary commands," researchers said in the paper. A malicious attacker can inject malware in the SOAP XML communication between the WSUS server and the client and making it look purely authentic update to install. Windows update also includes more than 25,000 of 3rd-party drivers that are developed and signed by other developers, which can also be altered easily. “Our concern is that when plugging in a USB device, some of these drivers may have vulnerabilities that could be exploited for malicious purposes. Everyone is familiar with the 'searching for Drivers' and ‘Windows Update' dialog boxes on their desktops – but these seemingly innocuous windows may be hiding some serious threats.” So, now it can be a big security threat for the new Windows 10. Either the corporates are going to live in the era of old Windows or upgrade and welcome the malware! The researchers demonstrated the hack at the Black Hat security conference in Las Vegas this week in a talk titled, WSUSpect: Compromising the Windows Enterprise via Windows Update. PDF Source: http://thehackernews.com/2015/08/windows-update-malware.html

Also take a look to this posts, they may be usefull too: http://www.msfn.org/board/topic/174149-we-can-hide-updates/#entry1104725 http://www.msfn.org/board/topic/174149-we-can-hide-updates/#entry1104859

I want to let you know about this comparative table:

If you have any concern about your privacy, you better make a reinstall and DO NOT use express settings, go one by one selecting your preferences.

The mathematical approach is this: 3000 % = 30 So shortening (or decrease) by 3000 % = 1/30 If your actual time is 100 seconds then 100/30 = 3.333 seconds. Oposite if you increase by 3000 % = *30 or 30x If your actual time is 100 seconds then 100 x 30 = 30000 seconds.

On cable conections you can try disabling the windows update service, and use the mentioned utility. I haven't tested this approach. This utility is free for home users: http://www.portableupdate.com/ From it you can check for updates, select what you want to download, and then it installs your selection if you want, It uses MS API's. I recomend to read all info in that page to learn how to use it.

If you are on WIFI you can permanently avoid downloading updates, valid for all versions. Go to config, select Internet, Wifi & Bluethoot, open WIFI, in advanced options select metered conection, (better reboot just in case). Then you can go to check for updates as usually but you only see what is available and no more updates download. I guess they made this option thinking in cell phones, tablets and laptops. Desktop is not a priority anymore. This utility is free for home users: http://www.portableupdate.com/ From it you can check for updates, select what you want to download, and then it installs your selection if you want, It uses MS API's. I recomend to read all info in that page to learn how to use it.

With same all due respect, you posted that info on January 16Th 2009, that is long time ago. Are you sure it is valid today? On the other hand this are known facts: Unless you own a Retail OS if you change MB you lose activation. (Retail can be installed on a diferent PC, maybe you need to call to get activated). So if you change MB in an OEM PC you lose activation, AFAIK only in Germany the law prohibits this, and there you can change MB without losing activation on an OEM PC. About changing HDD to SDD, MBR formated to GPT formated, x86 for x64, changing Graphic Card, add more RAM, I have read in other forum there is no problem to get automaticaly activated again when you reinstall, there were reports for people who did this for the fun to check. Best Regards

When you make an upgrade no key is required just run it from activated 7 SP-1 or 8.x. Then first time on line you get activated and HWID is stored on MS Activation Servers. (but anyway there is a generical key in your OS I checked that using aida64, same for everybody using same version). If during upgrade a key is requested, it means you are upgrading with the wrong version. Latter after upgrade, if you format and reinstall (clean install), the key is going to be requested twice, just skip it, DO NOT PUT ANY KEY, then when on line your OS gets activated automaticaly, as your HWID is already known. HWID I am sure you can change almost everything but if you change MB you lose activation. Old way to clean install the betas DO NOT WORK with these release (build10240). So if you don't make an upgrade first, you are not going to get activation (unless HWID is already known). You are free to make a local account, I recomend do not use express options, go one by one selecting you preferences, in order to protect your privacy as much as possible.

When you make an upgrade (or downgrade as you prefer to call it) to Win10 from an activated Win7SP-1 or 8.x, all Win10 Home Keys are the same for everybody (generical), same is for Pro, it is another key but also generical (every Pro has the same). You can use slmgr.vbs /dlv from a Command promt as administrator to see it says RETAIL not VL And slmgr.vbs /xpr from a Command promt as administrator to see it says PERMANENTLY ACTIVATED not as VL activation (180 days) I can confirm this: After the first activation you can format and reinstall (same version, not change from Home to Pro), even change HDD to SSD or change partions from Bios format to GPT (for UEFI) and just by skiping key (twice) during install once you are on line it will actvate automaticaly (Activation Servers are having high load now, be pattient) and you will get same key as before. You can also add more memory or change Grafic Card and no problem, Don't change MB because you lose activation. So machine ID must be tied to MB specifics as: ChipSet, MB Serial or Mak adress (if fixed on MB)

Windows 8.2 10 should have - more or less - the same hard disk space requirements as 8.1, i.e. between 16 and 20 Gb for a normal installation (wich BTW is more or less the same amount of space needed for Vista, Vista SP1, Vista SP 2, Vista SP3 WIndows 7 and windows 8: https://support.microsoft.com/en-us/kb/919183 http://windows.microsoft.com/en-us/windows7/products/system-requirements http://windows.microsoft.com/en-us/windows-8/system-requirements When the final version will be released, the new mechanism that is replacing wimboot: http://www.howtogeek.com/196416/wimboot-explained-how-windows-can-now-fit-on-a-tiny-16-gb-drive/ most probably will allow to make it much smaller (do not expect miracles, possibly a couple of Gb saved): https://www.thurrott.com/windows/windows-10/2062/microsoft-explains-os-compression-in-windows-10 cannot say if such mechanism is already available in these beta's . jaclaz Yes it is available in this betas, I already tried it, you get about 31% reduction in size from standard install (both witout pagefile and hiberfile), I tested it using WinNTSetup v3.80 to deploy the .wim to VHD see: http://www.msfn.org/board/topic/149612-winntsetup-v38/page-50#entry1101479 And also take a look to few latter posts, to clarify the use of this compact mode in WinNTSetup v3.80 To deploy Windows from Windows Setup Use an unattend.xml file with the setting: Microsoft-Windows-Setup\ImageInstall\OSImage\CompactMore info in Microsoft page about compact install: https://msdn.microsoft.com/en-us/library/windows/hardware/dn940129%28v=vs.85%29.aspx Best Regards

@ JFX Yes adk wimgapi.dll is in the tools folders (x86 and x64) it is v10.0.10075.0, downloaded first time I ran WinNTSetup 3.80 RC3 just to download required files as usual. The way I'm running it is this: I create a shortcut to WinNTSetup_x64.exe and open it with right button\properties and in the first line just add: " NT6 -compact" without quotes, then it starts in GUI, from the Win10x64 VHD it is working flawlessly, but not from Win7x86 or Win7x64 on HDD, it opens ok but can't apply the .wim, of course when in x86 I use WinNTSetup_x86.exe NT6 -compact "net start wofadk" command gives me "command not reconized". I think wofadk is not properly installed on my win7's, but i don't know how to do it yet. any ideas? Best Regards

I have WofADK driver in C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM\wofadk.sys Isn't it installed in that location?, Do I need to put it in system32?, Do I have to do something else? I had the idea that in order to make a compact mode install we need to mark the check box near to wimboot and I have done it during all my deployments, I guess that's why .wim had to be in same disk, so from your post I understand it is not necesary to mark that check box, Is it right? Best Regards

@JFX about v3.80RC3 1.- Tried to install a Win10 Insider preview last update from a Win7x64 to a VHD (located in internal HDD) compact mode from install.wim in HDD and it didn't work. 2.- Tried to install a Win10 Insider preview last update from a Win7x64 to a VHD (in USB HDD) compact mode from install.wim in USB HDD and it didn't work. 3.- Then I made a full install to VHD (located in internal HDD) from a Win7x64 install.wim in HDD and everything was OK. 4.- Latter booting from the Win10 IP x64 VHD (located in internal HDD) made a new VHD (in HDD) compact mode from install.wim in internal HDD and it worked flawlessly. 5.- Booting from Win10 IP x64 VHD (located in internal HDD) made a new VHD (in USB HDD) compact mode from install.wim in internal HDD and didn't work. 6.- Then booting from Win10 IP x64 VHD (located in internal HDD) made a new VHD (in USB HDD) compact mode from install.wim in USB HDD and it worked flawlessly. 7.- Latter I deleted install.wim (in USB & internal HDD's) and 4 & 6 booted just fine, so it is my guess the compact mode do not require an install.wim as it is a full install just compresed, so no pointer files to the .wim Acording to these it seams to me you can remove the requirement of install.wim in same HDD when compact mode installs, this can help to install in compact mode to USB 3.0 sticks in better time and less space required (as no need of install.wim in it). MY MISTAKE, I was doing it wrong way see post #1232 Also compact install do not work when you make an install from from Win7. Best Regards Note: I didn't put any links to external pages, they were created when I saved the post. I opened the compact install in VHD using 7Zip v9.38Beta, it is a full install but all files and folders are compressed as you can see in the attachment, (NTFS is not compressed just files and folders in it). Compact install in VHD is 5.70 GB (31.32% smaller) and standard install in VHD is 8.3 GB, (both not containing page file and hiberfile).

@JFX v3.80RC3 spanish translation: http://1drv.ms/1frgYn6

@JFX JFYI, there have been two updates to winlib v1.70 Beta last one 17 hours ago, first one is about behavior regarding exclusion of absolute links and last one is about improved the LZX compression performance during export operation by a further 10-15% Previous update: http://reboot.pro/topic/18345-wimlib-with-imagex-implementation/page-10#entry184745 Last update: http://reboot.pro/topic/18345-wimlib-with-imagex-implementation/page-11#entry184758 Regards

@JFX Would you please update first post in order to include all supported image formats? I rmember .wim, .esd, wimboot, but not sure about .swm (splited image), I don't know if I miss another one. Tanks in advance

@ JFX Thank you very much for the info, I'll try it ASAP.

Please explain a little the way to use it, i ran the v3.5 beta 1 and didn't see the option. Regards

JFX I re-updated Spanish translation v3beta3 to be consistent with with the new text format for Help file (Help text is now ASCII). http://www.mediafire.com/?bd97x287j7s8xaf Regards

JFX Attached link for Updated Spanish translation v3 Beta 3 http://www.mediafire.com/?oq9tnidvvm22h8l You should change first post it says: "Current Dev Version: v3 Beta1" Regards Edit: (see last version in post ·#681)

Attached link for Spanish translations v. 2.3.6.3 & v3 Beta http://www.mediafire.com/?h6zwh63lj796lc5 Help file was extracted, translated and reinjected folowing your instructions to 2058.dll ( the one that was created when I cliked "create translation" in v3 Beta. Best regards