From what I know when I edit the first post it makes it NOT hidden so I contact Tito (one of the mods) to fix it but when he does it breaks the thanks button. The reason the links are hidden is so mdl doesn't get takedown notices. I will report the first post again and maybe they can fix it...hoping nothing else breaks. lol Thanks for letting me know.
Thinking of adding to script to turn off win 10 spying off for win10 customers through all the services that run in the background. I have been reading all over and this seems to be a real popular subject and wanted by many. I will not be turning off apps and such like some tools out on the net because some use the calendar and such from metro apps. Those can easily be disabled using powershell if end users wish but I will not support that. I will add all hosts file entries I have and add it to the script to address the win10 spying issues. Does this sound ok to all?
From what i read so far, the hosts file is pretty much useless since Win 10 allows to over-ride those blocks to prevent the system from hosts file manipulations ... .
Can you share where you got that info from? I would like to read more on this subject. Please and thank you. From what I am reading its because they didn't clear the DNS cache and NetBIOS cache. If not done correctly like I have in the script it will fail...will test theory now in windows 10.
Seems most of the failures are with powershell not disabling items. I am not messing with that...only hosts entries. Testing some of the entries now to see. Plus I noticed he is only flushing dns cache and not NetBIOS as well which is sometimes required so it is good practice to do both to avoid issues. Also if hosts.ics or something like that is present then hosts file is by passed. Can check for that when done adding hosts entries. I will do major testing on my end before changing the original project script.
It's not that what i mean, it's the re-enabling/re-installing of reg-keys and services that seem to be very well protected.
This is another subject all together....I am not concerned with those since hosts blocks anyways...it will only being saving a few resources but end users can mess with that. I am not into modding but preventing as much info from going out. Either way I am testing now and will be for a few days then will report back. I will find the answers myself instead of third party ppl talking. Its better that way. Little hint: Windows 10 Home edition doesn't come with policy editor thus why the above tool fails. Policy editor was excluded from the Home edition on purpose. Hosts/Disabled Services is the best way to go because all that really matters is that no info is sent. You will still need to turn everything off under express settings during install but with the entries it does block most of it which is a plus to me. The less, the better. No need to worry about the hosts.ics since it is used on servers that use ICS. IT ppl know how to handle that (workstations then use the server with ICS hosts file instead of local).
I have original SLIC 2.1 in my Dell Inspiron 2310 bios (verified with SLIC toolkit 2.3 from my current OS Win8.1). I made a clean install of Win8.1 KMS activated removing my original Win7 Home Basic & Dell Recovery partition as i figured i wont be going back to Win7. But, now to avail free upgrade to Win10 from my genuine Win7 i want to get back OEM activation using the original SLIC in my bios. I've not backed up my activation (wasn't aware back then) but would like to save my unused COA Key also my COA is Home version which i want to avoid. Just wanted to confirm one thing that since I have SLIC 2.1 in my bios this OEM project should activate any version of Win7 (without using loader that is) and I'm not just limited to my Home Basic version assuming that the project includes the keys and certificates for all Win7 versions of my model/OEM i.e. Dell - is that correct? I'm thinking of upgrading from genuine Win7 Pro/Ult to Win10 Pro followed by a clean install of Win10.
@BALTAGY, again this is pro, enterprise editions not home thus that method would fail on home edition because of no policy editor. @SamSaha, If you already did clean install from win8.1 to win10 using kms activation then your HWID is already tied to the generic KMS key. No way to upgrade to pro unless you pay a little. Win10 is HWID tied in general...waiting to see if oem activation changes from win8.x to win10. This is what I have been told anyways. I don't use kms for windows 10 activation personally.
@BALTAGY, I sent you pm with a tool for you to test in win10...win10 installed edition is irrelevant.
Not yet upgraded to Win10, i'm contemplating going back from my Win8.1 KMS install to my genuine Win7 OEM activation before i make the upgrade to specifically avoid my "HWID being tied to the generic KMS key" just as you mentioned and be a target for any future crackdown via WAT update. Just want to know if i can get genuine Win7 Ultimate/Pro activation using this OEM Project or am i limited to activating only the Home Basic version that my Dell unit came installed with? After going through a several threads I got the impression that if there is SLIC2.1 in my BIOS and the OEM project has the certificates & keys for all versions of Win7 for my model/OEM then even though my unit came with Home Basic I can OEM activate genuine Win7 Pro/Ultimate using this OEM Media Project (without the use of SLIC emulation by Loader) as the SLIC2.1 is OEM specific and NOT variant specific as far as Win7 is concerned - am i correct?
Why not use this multi oem project for your win7 oem activation if slic 2.1 in your bios then upgrade to win10 with no worries about kms issues with windows 10 activations? I know it's more steps but worth it in the end I think. You are correct in your logic in the above post.
Thanx for your reply. So I should be able to OEM activate Win7 Ultimate instead of Home Basic and upgrade to Win10 Pro? Then its surely worth the hardwork. This forum is a fantastic place to learn these stuff, hats-off to you people!
Yes, win7 keys are edition specific not related to bios...only slic/cert has to do with the bios matching. Your good to go and good luck with the upgrade.
@BALTAGY, I will add logging to the script later on but wanted to test the specifics for right now. Keep me posted on progress in pm. I have some running around to do today so I will log back in later on today to see if you pm'd me. Take care everyone and have a wonderful day.
All done with testing as a separate script. I have incorporated the scripts together and maintained script speed, optimized hosts file speed suggested by s1ave77, added fix for traceroute and netstat display anomaly and added logging to the new sections of script with minor changes to improve stability. Testing the whole project now in VMware with all OS's, then will update first post tomorrow.