Integrate7 works fine. I create a new Windows 7 Professional SP1 64-bit install disc every time a new version is released. And I have never had a clean install fail when using it.
Cleaned up the thread a little. Please keep the discussion civilized. Spreading FUD without any proof is rather silly and immature.
It's called quality control. A work that I did, professionally, for years. Perhaps when more than a user face the same problem, what kind of proof you need more?
@acer-5100 The integrator script is written in batch, which means anyone can read the codes and verify the working principle. Besides, for a community development, we actually need more than one report with adequate background information to suspect a foul play.
You exactly know that antiviruses tend to block legal (non-malicious) tools from functioning. You have warned about this personally --> here , so you are aware of this. And yes, you should report these so called "false positives" to them. Instead you are spamming my thread and slandering me, with no reason. My script is a batch script, easy to read and investigate.
Still dont have proof of malicious intents. Find them first, you can read the entire batch and every row of code yourself lol
If you really want to criticize with a constructive mind, provide every little detail of your test setup so that others can replicate the issue. Otherwise, kindly stop spawning the useless drama.
Like I said I'm here to help anyone who deserves, like I did in the last 25 years spent on the net. But a person that instead of asking nicely about the test conditions, the ISO used to test, the host OS and whatever, the only thing that can write is "you are a noob", "all my programs are perfect" "the culprits are the antivirus" and other amenities like that, don't deserve my help. Pretty simple And no one is spamming, I just replied ONCE to an user who faced the same problem. And that triggered the usual hostility of wkellrer.
Maybe I,m wrong but Please stop all this noncence and stay on topic, make a new topic if people really want spamming with noncence, this is almost becoming a children-garden in all wkellers topic, are we grown people or children.
What you replied(and got deleted) was basically along the lines of "the only thing this script does right is corrupt the component store". A.k.a semi-sarcastic and also no real examples of the statement. I mean... you don't need to think too much to figure out how that's more likely to trigger a negative response rather than a constructive one... Also, when quality controlling, you most likely need to point out the actual problem, not just say there's a problem. I should know, I take in sort of RMAs and people either point out the problem, we reproduce it and we replace/refund, or people act arrogant while we find 0 problems with the returned product and get nowhere.
The following updates don't appear to download: ndp48-kb5020879-x64.exe ndp48-kb5028958-x64.exe windows6.1-kb5010798-x64.msu windows6.1-kb5013637-x64.msu windows6.1-kb5017397-x64.msu windows6.1-kb5020861-x64.msu windows6.1-kb5022338-x64.msu windows6.1-kb5028969-x64.msu windows6.1-kb5029296-x64.msu
~ I just tried some of those URLs - both in browser and via script = working ok (for me).. Perhaps temporary issue - make sure to delete any 0 byte files if leftover..
Hello everybody, while I am not technically using integrate7 script, I do study new versions of the script from time to time, and I admire wkeller's very hard work, zeal and passion to deliver it. This is some really good work - excuse me for stating the obvious. I have a small point. maybe not correct maybe correct, there is some activity in the script to reduce the telemetry in Win7, however at the same WU updates that introduce "inblockable" telemetry back-ported from Win10 are added by the script. my sources are here: getblackbird.net/documentation/ & getblackbird.net/blacklist/updates/ I do not have those installed and my win7 update seems to be working OK. or maybe I am missing something...
There is no such thing like "inblockable" telemetry in any Windows. Everything can be blocked/disabled/removed in Windows 7/8/10/11.
Are you sure? There are many links to various, apparently reputable sources on blackbird web page, did you had a chance to take a look, please? They all claim that Win10 introduced hard-cored methods that can be only blocked by filtering https requests on the router. And that method was then back-ported to win 7 and win 8. Maybe it is worth a while to take a look using wireshark or something? Otherwise that would mean Blackbird, ArsTechnica, Computerworld, ZDNet and other quoted there to spread FUD that would be bizarre...
I am sure. They are dead wrong and they are pseudo-experts. There is no need to use router, firewall, etc. to block telemetry, because it can be disabled other ways. Why do you assume that I haven't already done that ?
Not to depreciate wkeller's work in any way what so ever; he's very hard working, helpful (in contrast to a lot of people on this forum), offers one of the most user friendly ways to strip a lot of the user hostile crap out of Windows there is with Slimdown10 and except for his not really being very good about honoring FOSS licensure he's usually on target. With regard to Windows telemetry however, he may be mistaken; Windows has a lot of opaque and undocumented features, calls and triggers just like Intel's IME, and AMD's PSP. You can gut, block, remove, and turn off a lot of stuff in the OS installation, and get no quiescent measurable telemetry going out -- but some have pointed to certain applications or use cases triggering even the most neutered install to 'call home'. I have run WireShark and Omnipeak, and even tried probing things with Ettercap, and Slimdown10 (further curtailed with ReviOS's post install script) at least appears to be quiet, but that does not mean there's not something hidden away in the over a quarter of a million files that might leak something under circumstances no one is yet aware of... Windows is obviously not open source, where one can know what's going on... Caveat Emptor
I just wanted to take the opportunity to thank you for this great script. Really appreciate it and hope you will find the time to maybe release a November update