Sysinternals Site Migration


Hi, my name is Otto Helweg and I’m very excited to help lead the Sysinternals community migration as well as help define a plan for Sysinternals growth going forward. I’m a Program Manager in the Windows Server and Tools division but my background is heavy IT-Pro (not too much dev) and I look forward to interfacing with the Sysinternals users. Mark has been super helpful in guiding our planning for this migration and will continue to be involved in the post migrated site and ongoing development of its content.


 


Our goal is to smoothly migrate the major Sysinternals site components to Microsoft services and keep the same level of service the community received pre-acquisition. Here’s how the components are going to match up:


 

























Original Sysinternals Site


Microsoft Service


Mark’s Blog


TechNet Blog – Mark


Yahoo Groups Newsletter


TechNet Blog – Sysinternals


Web Site


TechNet TechCenter


Downloads


Microsoft.Com Downloads


Forum


TechNet Forum


Source Code


Not being migrated.


 


Once the Sysinternals site has been completely migrated and stabilized, we’re going to begin to implement plans on growing this community. What does that mean? Well, we’ve just starting thinking about this but we do know that Sysinternals has been very successful in reaching their customer base with free tools and utilities that assist in Windows troubleshooting. We would like to see if we could leverage this model across other parts of Microsoft as well. Look for more details after the first of the year.


 


Let me highlight the Sysinternals site components that will change – just so there are no surprises.


 


Mark’s Blog: Mark’s blog has been moved over to TechNet blogs. He will continue to post on the same topics as before (as time permits I’m sure). We will work on getting his blog history moved over as well (although we’re still trying to determine the feasibility of migrating the blog comments). His new blog is: http://blogs.technet.com/MarkRussinovich


 


Newsletter: Going forward, we will be publishing the newsletter in the form of a blog. We feel a blog would be better since it can still be syndicated (trough RSS or ATOM) and it allows for folks to comment. This blog content will be primarily focused on site changes and updates during and post migration. The site blog is: http://blogs.technet.com/sysinternals


 


Web Site: Starting out we are going to be creating a TechCenter on the TechNet site dedicated to Sysinternals and containing the main Sysinternals pages. If we miss migrating important sections of the original Sysinternals site, we will migrate those after the fact as demand surfaces. We will initially maintain a site support e-mail address (syssite@microsoft.com) to address initial site issues.


 


Downloads: We will be migrating most Sysinternals tools to Microsoft.Com Downloads which has additional bandwidth for a better end-user experience. At Mark’s direction, we are not going to be migrating 100% of the tools for one of the following reasons:


 


1.     It only worked on Win9x or DOS – the number of downloads didn’t justify the migration. These were eventually going to be removed from Sysinternals anyway.


2.     Not compatible with XP or Vista – or had compatibility issues with other 3rd party applications and were slated for removal pre-acquisition.


3.     Demo tools – some tools were posted as demos that were paired with Mark’s articles. We are still trying to determine where these will land.


 


If you want a tool back, let us know and we’ll let community demand help drive our priorities.


 


We have also changed the Licensing Terms and made it ‘click-through’. The Licensing Terms are actually more liberal and are intended to allow the tools to be used in more situations without a custom license.


 


Forum: The Forum will be the last site component to migrate due to its complexity. The new TechNet Forum for Sysinternals will essentially have the same structure. In addition, the moderators have agreed to keep their roles as moderators in TechNet as well! We are going to try to migrate all the Forums history, but we know that data quality will suffer to some degree (e.g. reference links within replies may be broken). In addition we won’t be able to migrate Forum accounts, so participants will need to re-register with TechNet.


 


Source Code: The number of source code downloads didn’t justify the migration, support, and possible integration problems it might cause with other Windows components down the road.


Comments (139)

  1. Anonymous says:

    Here’s an announcement that I almost missed due to the noise from TechEd and the Sysinternals site migration.

  2. Anonymous says:

    Yes, the old files are still on the downloads.sysinternals.com site and the old links are still active. They will gradually dissappear as we migrate more of the site over.

  3. Anonymous says:

    Congratulation :)

    Process Explorer want to keep too !

    Regards.

  4. Anonymous says:

    今年の7月にMSに買われた Sysinternals サイトの各種公開ソースコードの行方ですが・・・

  5. Anonymous says:

    From Windows Systernals Technet Blog: Our goal is to smoothly migrate the major Sysinternals site components

  6. Anonymous says:

    Microsoft withdraws Sysinternals source code

  7. Anonymous says:

    Mitte des Jahres wurde Winternals und Sysinternals von Microsoft gekauft. Das Angebot der sehr hilfreichen Tools steht auch heute noch kostenlos zur Verfügung. In den vergangenen Tagen wurden nun die letzten Vorkehrungen getroffen um das neue Angebot

  8. Anonymous says:

    Anonymous: They’re not quite lying.  What they aren’t saying is that no number of downloads would’ve justified the migration, even if millions of people were downloading it.

  9. Anonymous says:

    Please see my comment "If you want a tool back, let us know and we’ll let community demand help drive our priorities." I’m willing to apply that to the source code as well. It would be helpful to hear why source code access is important (please be specific) and which source code has been the most helpful. Some code may be easier for us to post than other code and this will help drive its priority.

    I have been and will continue to be open and honest with you (the community) about our decisions and directions with Sysinternals. I maintain that the current source code decision is driven more by resources and priorities than it is about policy.

    I want to see this community grow at Microsoft, not just exist.

  10. Anonymous says:

    I must agree with Legolas.  For the SysInternals software that is usable for malware authors, binary forms are plenty usable.  The malware writers don’t have to know how it works, they can just call it.  For legitimate research, though, there’s significant purpose in the source code.

    I too can understand the desire to avoid undocumented APIs, but I must concur with other posters: the tools should use alternative methods when they exist, but if the undocumented way is the only way, then let us see the gory details and preface it with one of those nasty "This code uses undocumented APIs that will disappear if/when we wish."

    I also concur with Legolas that the necessity for the SysInternals tools to use undocumented APIs should be used as a guide to add documented means of accessing these capabilities to future versions of Windows.

    More code in technical articles is always helpful, but I would still prefer the full code be posted.

  11. Anonymous says:

    Looks like the SysInternals Website is preparing for a Site Migration , having been acquired by Microsoft

  12. Anonymous says:

    Hey Folks,

    1) Mark is on board with this decision

    2) We have some internal policies – which I believe are reasonable (although sometimes tedious) – to bring code through a review process before providing it to our customers so they don’t get bitten by issues like API changes between operating systems. This process alone requires resources, not to mention the efforts, involved in updating comments, API calls, coding practices etc., so we have a level of confidence that we’re not doing our customers a disservice. In addition, we don’t want to send a mixed message by providing code that goes against some of our own published (and followed) best practices (like not using private APIs). I know the historical Sysinternals members can overlook this, but I’m driven by a baseline that includes our entire customer base that may not be familiar with these tools or their history.

    3) Our resources are tapped out trying to get this site up and will be for the next couple months. Right now my driver is the 600,000 daily visits to the site and trying to ease that transition experience. In addition, Mark and Bryce are revving bits, sometimes several times a day, which are fixing bugs and issues as they flow in from this new launch. Adding un-scoped features like source code is not at the top of my agenda right now. Getting a better understanding of the source code usage scenarios would help me elevate it.

    I’m asking you to work with me on this, not against me.

  13. Anonymous says:

    It’s started. The entire Sysinternals site has been flagged to be migrated into various areas of

  14. Anonymous says:

    Unfortunately, it doesn’t suprise me that they pulled the source code.

    Maybe thats why we killed the servers in the days after the announcement.  All of us were either downloading the tools like crazy and/or copying the whole websie.

    We were worried about losing the great work that Mark did.  

    I for one, copied the entire website (including the source code).

    Come on Microsoft … wake up … the source code is a big part of what made the site great.

    Of course the number of downloads for source code wasn’t as big of a nubmer as the tools.  Tools got downloaded as they were used.  Source code was only downloaded as we needed to reference them to try to figure out how Mark did his magic.

    Please (For the sake of those who didn’t see this coming) restore the source code and for the sake of all of us … continue to update the source code.  Its not just about what was already there, but the future as well, keep the source code current.

  15. Anonymous says:

    I have to add another vote … Source code is very important.

  16. Anonymous says:

    It looks like there’s a lot of churn over the source code issue. Let me say that it was not an immediate decision and there was debate over whether or not to post the source code. Some of the other reasons for not posting it include the fact that it has been used in malware, and some of the programs use undocumented APIs (which we’re trying to get away from).

    Would it be acceptable to start including more source code chunks in the blog and information articles instead?

    We are interested in your opinions. Thanks for posting.

  17. McAkins says:

    We are glad Microsoft has decided to keep and improved on SysInternals objectives. We are looking forward to the improvements MS will make on these tools. I am sure it will help make MS platform more attractive.

    My congratulations to Mark and his colleagues on this acquisition.

  18. Green says:

    "1. It only worked on Win9x or DOS – the number of downloads didn’t justify the migration. These were eventually going to be removed from Sysinternals anyway.

    2. Not compatible with XP or Vista – or had compatibility issues with other 3rd party applications and were slated for removal pre-acquisition."

    It’s wierd how Microsoft doesn’t want to support it’s own operating system… No wait it isn’t. Policy like this don’t get my points.

  19. GNU/Linux says:

    Would be a GNU/Linux sysinternals tools?

  20. Josh K says:

    I don’t see why it would be difficult to migrate the source code, if they’re going to migrate the compiled versions…

  21. g-n-d.net says:

    Mark , source code is very important for us ! ! !, and I think it woudn’t be difficult migrate the source code, so,…, try to help us, please .

  22. Alexey D says:

    > Source Code: The number of source code downloads

    > didn’t justify the migration, support, and

    > possible integration problems it might cause

    > with other Windows components down the road.

    This to me sounds like "don’t worry guys – there will be no source code from now on". From my point of view the value of SysInternals and everything that Mark was doing was in that it was open and insightful. The source code illustrated some aspects of internals of Windows together with Mark’s explanations and articles.  But now I’m afraid the openness will be gone – only tools will remain. "Well" done – typical Microsoft style.

  23. Anonymous says:

    "Source Code: The number of source code downloads didn’t justify the migration, support, and possible integration problems it might cause with other Windows components down the road."

    Lying through your teeth.

    Honest would’ve been: Only Microsoft should have the chance of even remotely, somehow, making any kind of gain from this, except for when you’re using what we give you, and how we tell you to.

  24. Max says:

    Agreed, source code is a must!

  25. Mata says:

    No source code :(

    Well I hope the $ tastes good

  26. Legolas says:

    If these tools use undocumented API’s, fix the source code and post it afterwards (and DO fix it). If it’s not fixable, well, then that points to a problem in the windows API no?

    The fact that it has been used in malware, well, how about you don’t make any API available, because they to are certainly used in malware.

    For me, it always felt ‘safe’ to have the sourcecode available: if I ever need to do something like that, I can look at the code here. Real life code, not marketing samples that ignore pretty much everything you have in real software. And otoh, I knew the tool probably wasn’t doing anything malicious, since certainly someone read the source and checked.

    Why not talk to the MSDN people? I’m sure they’d love to have some very advanced samples of using the API available…

  27. andreyd says:

    I do not think that by not migrating the source code they can avoid malware development. The source has been there for years. The guys that write malware already have it. And also there is a full community(ies) of reverse engineering people.

    By not releasing the source they are actually hurting the new developers. People that for some reason want to understand how Windows works or have/need to write a driver.

    I really hope they post the source again for the benefit of the developer community. (And mine too, since I don’t remember where I put the sources :))

  28. mark says:

    Please, i think the decision to not migrate the source is a bad one, and the  excuses given, (malware) ridiculous. and (too much work) are already making me lose faith in the transition, it sounds like censorship from day one! The source is very useful as a reference.

  29. Anonymous says:

    Aha, malware. Tell me: Why are american civilians allowed to use guns? Surely they could be mal-used as well? I’m very sorry to say, but i still think you’re lying, mainly because i can not believe that any human being could actually state that as a reason for keeping source-code out AND actualle believe it.

    Regarding undocumented APIs: There are three things one could do here.

    A) Document them and make them something useful.

    B) Replace them with something that fits the windows vision or something.

    C) Try to hide them for some reason, god forbid people use your hacks for something useful.

    Are you sure you want to choose C)?

    Acceptable to post code chunks? Yes and no. YYes, it would be a TINY step in the general direction could approximately be described as right. No because it means that we get alms from the benevolent Microsoft as he sees fit to hand out instead of the free sharing of mind and creation that was previously what the name Sysinternals meant.

    The correct thing to do without hurting your code integrity (heh): Ask Mark Russinovich about the source code he created and had decided to share with the community of windows users. If he still desires to share it, put it up in an archive, marked as deprecated, unsupported and for learning purposes only.

    Anything else will most likely only cement the image that the general public has of you even further.

  30. Bill says:

    Mark can you send me all the source code? taywaileong@hotmail.com

  31. jawz101 says:

    It only seems fitting that sourcecode should now be accessible on MSDN Academic Alliance site or MSDN Developer’s site if anywhere.

  32. Eddy Carroll says:

    I’m a longtime user of Mark & Bryce’s excellent tools. I can sum up their best points as:

     – Good design, excellent reliability, superior engineering

     – As non-intrusive as possible on the system – one of the early pioneers of dynamically loadable device drivers, for example

     – Excellent reference apps for other developers looking to follow good practise

    If Microsoft chooses not to migrate over the source code along with the main apps, they will be giving up a hugely valuable resource for developers.

    It only takes one developer to write an application that may be used by hundreds or thousands of users. Mark & Bryce have provided working examples of how to implement a whole range of sophisticated Windows programming techniques, and a whole generation of developers have benefited from this.

    Posting code snippets is not remotely as useful as showing a fully working application. Making the source code only available through a closed Microsoft developer program is also nowhere near as useful.

    If Microsoft wishes to retain the respect of the development community during the course of this acquisition, source code MUST continue to be made readily available. I hope this is clear from the other comments already posted.

  33. Martin says:

    One more vote … please keep source code available.

  34. K.L.C. says:

    IF YOU DON’T GIVE US THE SOURCE CODE BACK WE DEVELOPERS WILL NEVER TRUST YOU AGAIN.

    THIS IS A CHANCE FOR MICROSOFT TO GAIN BACK SOME OF OUR TRUST, IN THAT, YOU’LL DO THE RIGHT THING.

    DON’T BLOW IT!

    THERE ARE A LOT OF IMPORTANT DEVELOPERS, SUPPORTERS, AND INDIVIDUALS HERE THAT USE AND READ SYSINTERNALS.

    MANY WITHIN YOU OWN COMPANY (Can they speak-up like this? I don’t know), AND MANY WITHIN OTHER COUNTRIES

    (E.G. You want European developers to stick up for you when their country is trying to sue you into oblivion, then don’t screw your supporter; developers.)

    YOU NEED US AS ADVOCATES FOR DEVELOPMENT OF MICROSOFT CENTERED SOFTWARE.

    WE WILL STAND BEHIND YOU, BUT YOU HAVE GOT TO MEET US ON NEUTRAL GROUND.

    WERE NOT IN THE .000001% CATEGORY OF MALWARE WRITERS.

    "SACRIFICE THE MANY FOR THE FEW".

    SOUNDS LIKE THE ENTERTAINMENT INDUSTRY’S APPROACH DOESN’T IT.

    WE ALL KNOW HOW THAT’S WORKING OUT.

    YES, I’M YELLING, BECAUSE I’M MAD AS HELL.

    SHOW US YOU CARE!!!! DO THE RIGHT THING!!!!

    Please do the right thing.

    K.L.C.

  35. Robert Love says:

    If you have to use the undocumented API’s to pull off what is needed for SysInternals then they need to be documented.   Otherwise our applications are on a Level playing field with Microsoft.      

    Source code, is educational.  

    I am a software developer and we use SysInternals Products all of the time.    

    I see your from the IT side of the house.  

    I wish Sysinternals was acquired now and placed in MSDN instead of Technet!   We view it as a valuable development tool more than an IT tool.  

    Snippets on the blog just don’t count, as I then have to search multiple blog entries that are pointless to find the way something was done in a sysinternals product, I might not even find it.   I think that posting snippets in blogs is an excellent additional to the source code.

  36. GregM says:

    I absolutely agree about the undocumented code.  If there isn’t already a documented method to do what the undocumented code was doing, then document the method so it is no longer undocumented, mark it as deprecated in future versions of the OS, and add a "supported" method for doing it.

  37. sean says:

    Yet another shout against the bogus reasons…

  38. Jaap van Ginkel says:

    Another disappointment in Microsoft the source code disappears.

    I even defended the "takeover" and believed sysinternals would be safe.

    Ah well it’s Marks decission to let this happen.

    All the fuzz will probably result in the source code being available a little longer but in the end I’m just loosing my trust in Microsoft.

    I feel powerless the only small thing I can do

    is remove the terrible Vista from a few machines  and replace it with Ubuntu although they already devoured Novell/Suse so where is the end….

  39. Greg Hardt says:

    On the site move:

    I’m very disappointed that the SysInternals.com domain is completely gone. Most sites post up notice that there will be a merge, and typically the old content is still accessible for months afterward. This is prohibition: download from SysInternals.com in October, search Microsoft hopelessly in November. *sigh*  Could we please get SysInternals.com back up for a week?

    On the source code:

    Open source has always meant three things to me:

    * No mal intent or hidden agenda (to quote Steak & Shake “If it’s in sight, it must be right!”)

    * quick patches to bugs (if not by the developer, then by the user community)

    * fully extensible

    Some would say that open source programs are more secure. This is not so by the virtue of just posting the code, but becomes so over time because of value #2 above.

    I’m not a developer any more, and have little use for the source code now. However, that does not minimize any of the three values above. And having done software development I can truthfully say that proprietary software derives a LOT of its value due to the need to reverse engineer the “undocumented APIs” in order to provide desperately needed functionality in today’s ubiquitous mixed environments. Mainframe & server farm, Mainframe & Web/XML, Microsoft & Linux, data mining apps that pull from both SQL Server and Oracle systems… on and on. Most vendors provide little help in these situations, and the majority of retail books are worse than worthless. It is the rare gems like SysInternals.com, AutoIt, SourceForge, etc. that enable and drive today’s IT.

    Ultimately, the enveloping of SysInternals into Microsoft will be seen as just one more innovation that Microsoft bought to control and claim as its own because they were unable to innovate on their own.

    Ottoh,

    * Put SysInternals.com back up for a couple of weeks to ease the transition for those like myself that visited only once a month and may have missed any advance notice.

    * Don’t be afraid of the posting source – free the source and be set free yourself from worries about the source. Your community will catch an errors you miss, and will help you with security problems as they arise.

    * Lastly, and perhaps most importantly, listen to your community. Ultimately innovation is just meeting needs. (Not to be confused with sales: an attempt to convince customers that they have a need.)

  40. Greg Hardt says:

    Ottoh, thanks for the opportunity to provide feedback. It was good to see a reply from you yesterday. :)

  41. sean says:

    New EULAs too!

    You may not:

    * work around any technical limitations in the binary versions of the software;

    * reverse engineer, decompile or disassemble the binary versions of the software, except and only to the extent that

    applicable law expressly permits, despite this limitation;

  42. DisappointedOne says:

    Rushing in and downloading all the source code from the old SysInternals site the moment I heard about the ‘migration’ to Microsoft… now *that* was a good decision, wasn’t it? Can’t stop congratulating myself on it.

    On the ‘Oh my, used in malware, cut it, cut it!!!’ issue: The only thing you’ll accomplish will be to have all those sources floating around on hacker sites, file sharing networks and the like. Many people who could do something useful with them may not be bothered to search for them in those places, but malware authors most certainly will. Who’s losing and who’s gaining, I wonder?

    On the undocumented APIs issue: instead of moving towards eliminating any trace of references to those pesky APIs, how about trying the opposite direction for a change? Let’s face it: some tools can’t be as powerful as they need to be without access to some undocumented parts of the OS. Having such tools available ultimately makes the OS more useful to IT professionals. You should be helping the development of such tools, not hinder it. Of course there’s the caveat that the APIs are not officially supported, may change in the next version, and so on, but everybody knows that; the tools will simply be updated to cope with the changes, if they ever happen – and we all know it’s not that often anyway.

    In summary, I’ve yet to hear a valid reason for not migrating the source code. Until I do, I’ll remain extremely disappointed to see MS is still headed in the old, wrong, direction.

    And no, code snippets in blogs won’t cut it.

  43. Karl says:

    The lack of source code seems like a slap in the face. From the Winternals acquisition press release:

    "Customers will be able to continue building on Sysinternals’ advanced utilities, technical information and source code for utilities related to Windows."

    So, the source code bit was just a lie? This really makes me distrust Microsoft’s intentions with SysInternals. At a moment’s notice, other things could begin to disappear. Do I have to mirror the entire site now?

    I’ve found the source code to be immensely useful, from understanding how Windows works, to adding features to NewSID to streamline our image deployment process (which is a giant pain without third-party tools, and even if Vista fixes this, the massive changes in Vista requires us to delay adoption).

    Some of the tools used undocumented APIs (which, as other people pointed out, only shows the limitations of the documented API), but a lot of them didn’t. Many showed how to properly use the security APIs, etc., and fills many gaps left by the SDK.

    Please bring the source back. Add disclaimers up the wazoo if you’d like, or just add them to the Windows SDK examples. But please, bring the source back!

  44. Bob says:

    I really think one of the most importantant aspects of the heart and soul of sysinternals has been done a great disservice by removing the source code. In my opinion, one of the greatest ideas of the site was the education about and illumination of Windows systems internals as illustrated by the code examples. What better way to show this than by example and having the code to look at when trying to understand the issues being discussed was invaluable. SHAME ON WHOEVER DECIDED TO ELIMINATE THIS TREMENDOUS RESOURCE!!!!! BRING IT BACK!!!! BRING IT BACK!!!! BRING IT BACK!!!!!

  45. Old Man says:

    I am not a developer so I have not made use of Mark & Bryce’s source code, although as a long-time IT pro I can readily understand its usefulness.  

    My concern is for the tools themselves. I have been a patron of the Sysinternals site for a number of years, and watched the number and usefulness of their tools increase. Also, through various employers (NOT Best Buy), I have purchased various Winternals tools.  Mark and Bryce were one of my trusted sources for unbiased, functional information, and truly useful tools I couldn’t find elsewhere.  

    Call me a conspiracy theorist, but I fear that Microsoft has, in part, acquired Sysinternals to stifle two obviously brilliant minds who thought outside the box. They are independent thinkers who have specialized in dissecting Microsoft’s API’s and making something useful out of them. Look what they did for the Sony rootkit debacle.  Even though it was supposedly discovered by someone else, Mark has received the majority of the credit for exposing it.  It would appear that, to eliminate their nuisance alluded to by Otto’s “undocumented API” comment; Microsoft just used its money to acquire the company, thereby telling Mark and Bryce to shut up.

    Yes, Mark and Bryce can continue to do wonderful things. If these guys can’t find a tool for something they need, they just write one. Only instead of doing them for the benefit of the user community, they’ll do them for Microsoft!  Now that the company essentially controls what gets published, I fear that the pairs best work, which many of us have come to rely on, will now be kept internally and not made available outside the hallowed Redmond walls, with the stated excuse of “malware” or some other equally lame reasoning.

    Rolling Sysinternals tools into Microsoft Download is just the absolute kicker for essentially killing what used to be a very useful resource.  We’ll have “Genuine Windows Advantage” or whatever it’s called, licensing keyed to all the tools, when we can find them.  Having the tool listings and version information on RSS was SO simple (with apologies to GEICO) even a Cave Man could find them and readily figure out if there was a new version or new tool to download.  Now we will have to find them and figure the versioning out for ourselves.

    I’ll get off my soapbox now, Ciao!

  46. Old Man says:

    It would appear that I shot my mouth off before thoroughly researching the new site, and as such I apologize for the hastiness of my criticism!

    At current juncture I withdraw my apparently unwarranted attack on killing the Sysinternals website. I will wander the new TechNet site for awhile and see what is for free in curiosity!

  47. steelbytes says:

    even please post the source code in an unsupported as is state.  even with out keeping it upto date with the binarys.  or are we supposed to have a black market to get the source code that was there until a week ago?

  48. anonymous says:

    So now the source of windows insight will sites like the 29a labs <virus writing site, enter at your own risk>?

  49. John says:

    Sorry Microsoft, but taking freely available source code and then denying everyone access is not playing nice. No  one agrees with your reasons for doing so and o be honest, from past experience the reasons stated do not seem to be the truth. Obscure EULA’s are nasty too, there were more pros than cons when it was available in the past so why would the community’s approach all the sudden change…If you want our support then you have to play nice…  

  50. Ryan says:

    Hah!! I tried to post the old links to the source code here and it must have been moderated. Lame…  the site’s pages are still cached on Google… get em while you can

  51. Ryan says:

    Well, it must have been automatically stripped because of the web addresses, so just at tack http://download.sysinternals.com/Files/ on the front of the filenames and the links should work

  52. Ryan says:

    AccessEnum.zip

    AccessEnumSource.zip

    AdRestore.zip

    AdRestoreSource.zip

    Autologon.zip

    AutologonSource.zip

    CacheSet.zip

    CacheSetSource.zip

    Ctrl2Cap.zip

    Ctrl2CapSource.zip

    SecDemo.zip

    SecDemoSource.zip

    DiskExt.zip

    fmifs.zip

    Fundelete.exe

    FundeleteSource.zip

  53. Ryan says:

    A few more… I have all the links for stuff that was on the source code page

    Junction.zip

    JunctionSource.zip

    NewSid.zip

    NewSidSource.zip

    NtfsInfo.zip

    NtfsInfoSource.zip

    procfeatures.zip

    SDelete.zip

    SDeleteSource.zip

    ShareEnum.zip

    ShareEnumSource.zip

    TcpView.zip

    NetstatpSource.zip

    PipeList.zip

    PhysMem.zip

    RegHide.zip

    Tokenmon.zip

    TokenmonSource.zip

    TVcache.zip

    VcMon.zip

    VcMonSource.zip

    VxDMon.zip

    VxDMonSource.zip

  54. Ryan says:

    And finally a couple of oddballs…

    http://www.sysinternals.com/Files / Defrag.zip

    http://www.sysinternals.com/Files / DiskKey.zip

    delete the space

  55. Sanders says:

    Next:

    McAffee (av)

    Symantec (av)

    Skype

    Adobe

    Once the previous ones are gone, those are next on the menu:

    Autodesk

    Citrix

  56. Dinkum says:

    Well thank goodness for archive.org. I figured there was no more room under Microsoft’s rug for sweeping, but I guess those few megs of source code could _just_ get squeezed in there.

    It’s clear by the previous posts that the source code files still exist in the same root directory as the presently available tools from the updated site. Statements to the effect that it would be difficult to migrate suggests the migration team finds it difficult to keep the source code hyperlinks on the page they originally copied.

    I can understand Microsoft’s intentions with removing access to something they do not officially document, support, or perhaps condone. Misrepresenting about why, however, is not kosher in my book.

  57. Paul Thunder says:

    Sysinternals is moving to Micro$oft.

    I think Micro$oft has shafted us enough. The one place we though we could trust was Sysinternals, now I am wondering if Bill Gates showed you the light $$$,$$$,$$$.$$ and you said sold!.

    Which I hate to say, why migrate? Why not just stay an independent, with freedom there of.

    Mark you are those most awesome of coders please do not take my words wrong. I just do not want to see you sucked in the death machine (M$).

    I am surprised you are not going to Linux.

    Everyone I know is steering away from Microsoft, and heading to Linux.

    Either way Mark your still an awesome coder, I will miss your news letters, and programs, great technical advice that took me many years to try understand but I did.

    I learned from you.

    You are awesome!.

    However I have my own "FORD" Fix or Repair Daily "Microsoft Windows XP Pro"

    Good bye my friend I wish you well.

  58. Jeff Stein says:

    Boo on Microsoft!  Removing the source code (and some of the utilities, such as FileMon for Linux) is terrible.  And bald-face lying about it makes you look even worse!  Please stop buying innovative little companies just to destroy them.

  59. lewirp41 says:

    I agree with andreyd’s post… those who will use the source for malfeasence already have it. Those of us wanting it for educational are kicking ourselves for not downloading it while we had the chance. I have been an avid visiter to the Sysinternals site for the past year, but I only downloaded the executables … I never leave home without these tools before heading to work as an IT admin. Would like to get back in to coding and see the source (or a subset of it) made available again.

  60. Anonymous says:

    Ottoh, you’re asking us to beg you.

    And you’re doing so to see just how much you need to give us so we will shut up and let you delete the rest.

    I’ll give you the last bit of benefit of the doubt that i possess tho and ask this, hoping you are able to answer honestly for a change:

    What priorities are you talking about? What is so difficult about getting a few files, putting them on the new server and linking them? Do you not have enough ressources to handle the few megabytes? Are you running on 2000 Baud modems or something? Do you need to fill in a triplicate form for each link you put up?

    Also, most importantly: What does Mark say about this? Would he even be allowed to say something?

  61. Ben says:

    Ottoh,

    The key to this situation is that microsoft is as open as possible about the rational behind key decisions such as these. I know you have tried to do this, but if its a technical or ‘resources’ issue, tell us why there the process is a resource issue. If its some lengthy microsoft process for getting files posted the download.microsoft.com, then fine, but do tell us this.

    Right now as far as we know, its a simple matter of uploading them to a microsoft download server and posting a link to it… which would take about 15 minutes… so there must be more to it.

  62. Dave says:

    Ottoh,

    I wouldn’t expect Microsoft to "get it" on this issue. But as you can see – there is a community demand – if you were honest in your statement that "I’m willing to apply that to the source code as well" then you would have migrated the source long long before now.

    You seem to be implying that it would be somehow onerous to have code on your site, yet I can fine a LOT of obsolete documents on technet (just looked up DOS 6.0 debug command documentation – how handy).

    The source code – ALL of it – gives audit and educative opportunities.

    If you don’t recognize a community demand by now then there is absolutely no chance of you nurturing a community going forward. You may develop a group of people who appreciate the  sysinternal tools as they are released but don’t be silly enough to confuse that with a community.

  63. db says:

    Internal politics?

    Quality Assurance to make sure that "typical" (ie not sysinternal regulars) Microsoft developers are not lead astray and mislead? Paalllleeesse – give me a break!!

    Put the source code up.

    Then put up a bloody huge disclaimer with links to coding standards, and put it into every zip file. … hell maybe you can get "the community" to even help identify problems and do some auditing for you.

    If no one actually cares about the code (as you imply in the face of all of this) then nothings wrong, no harm-no foul. BUT If people look and find stuff – and then let you know, then you win  you save some auditing "resources" (green folding stuff) and hey … maybe by doing that you DO encourage a community rather than a user-base.

    In the mean time I am sooo glad I downloaded all source files earlier. And thanks to those who put up the links above – I filled a couple of gaps there.

  64. Mike says:

    “In addition, we don’t want to send a mixed message by providing code that goes against some of our own published (and followed) best practices (like not using private APIs).”

    But you are already sending mixed messages by providing binaries based on such code. It is okay for MS to use such code but not us? Great. :-

    Although I guess that must be a great way to limit competition.  

    Some of us come to sysinternals to learn how to do some of the neat things that Mark do. The source code was a huge part of the learning process. Since most of us only need to learn something once or twice the source code does not get downloaded nearly as often as the tools that we use all the time.

    The removal of source code makes me worried that sysinternals will be reduced to just another tool site. More source code in the articles would be great but it can not measure up to the full source code.

    Among the neat things we want to learn about are the undocumented things. Although i don’t think we would complain as much about losing the undocumented parts if we were shown how to do the same thing with official methods.

    I am not asking you to make the source code a top priority or anything. Just assurances that it will come back in some form would be nice.

  65. Anonymous says:

    I see you are a skilled forum warrior. You are well-versed in the skills of circumventing questions with half answers.

    (fine, mark is on the board, we all know that he is there, after all this is all HIS, no matter how hard ms tries to slap their corporate branding on, but that doesn’t answer what he THINKS about this. in retrospect, the question is pretty stupid though. it’s not as if a sane person can expect him to ever be able to speak his real opinion again as a part of microsoft. you realize that by this whole thing you have managed to taint everything he ever says from this point onwards?)

    You are well-versed in the skills of providing answers that make perfect sense when viewed from a very tight angle.

    (pro-tip: users != developers != customers)

    You are lastly well versed in the skills of talking in big words.

    (You’re talking about a simple website here, not an operating system… This isn’t rocket science.)

    Sadly you have left behind what is usually called "common human sense" and are left unable of thinking outside of your little corporate frame.

    Good bye.

  66. TanMan says:

    "Getting a better understanding of the source code usage scenarios would help me elevate it."

    Ottoh, everyone’s been telling you about how Mark’s source code is an INVALUABLE learning tool. We’re coders, creators of tools, not tech’s, users of tools. That’s why Mark posted his code – so coders could all learn from his example. And many of the techniques he uses are not available anywhere else, and certainly not from MS. And MS still feels this is not important?

    Re the fact that he sometimes uses undocumented techniques in his code, why is it you think he does that? Is it because MS provides a better way to get that information? No, it’s because MS DOESN’T provide a better way. As coders, we come up against the same obstacles, and Mark’s code can sometimes show us the way.

    "I’m asking you to work with me on this, not against me."

    Ottoh, we all are humbled at the feet of the master (Mark, that is), and what you are hearing is our resentment at having lost our master. Mark has helped us understand the maze which is Windows for many years. We see the knowledge Mark passed on now being cleansed by MS, and many of us are angry about this loss.

    We all wish Mark (and Bryce) well, and hope they are enjoying the fruits of their talent with MS. But, Ottoh, we don’t want to lose unfettered access to Mark. And we’re afraid that’s what’s happening.

    So, Ottoh, help use retain access to Mark and ALL the knowledge he wishes to share, not just the knowledge that is cleansed by MS. Work with us, not against us, and you will feel the undying gratitude of us coders instead of the anger you now perceive.

    Thanks,

    TanMan

  67. Ryan says:

    Mark, you have totally sold yourself and your work to MS. Your/Their recent decisons are not helpful to the general community.

    "Some of the other reasons for not posting it [source code] include the fact that it has been used in malware, and some of the programs use undocumented APIs (which we’re trying to get away from)."

    A lot of public code is used in malware. So what? It’s not like if the code wasn’t there, it’s going to stop people from writing malware. If it takes advantages of flaws in the OS, then it’s the OS that needs to be fixed instead of hiding the code that shows it.

    As for undocumented APIs, who cares? You used them in making it, but you’re saying it’s bad to show other people even if you give a blatant warning? The APIs need to be documented. Having undocumented APIs is the fault of the API creators, so it’s their job to fix it.

  68. Ryan says:

    Hmm…buying out a developer, removing source code and non-Windows tools, not listening to the people…why does this sound so familiar? Ah yes…it’s MS again!

    Removing code & utilities that was previously available makes sense, why? Has ANYBODY ever complained that the source code being available for download was harmful (for reasons other than those that are against all open-source code)? How many requests have been made to make the existing code and tools available? Yeah…you’re really listening to what the community wants.

    "I’m asking you to work with me on this, not against me."

    It’s hard to work with somebody who is obviously not listening to us.

  69. AngryBrit says:

    <blockquote>Hey Folks,

    1) Mark is on board with this decision

    2) We have some internal policies – which I believe are reasonable (although sometimes tedious) – to bring code through a review process before providing it to our customers so they don’t get bitten by issues like API changes between operating systems. This process alone requires resources, not to mention the efforts, involved in updating comments, API calls, coding practices etc., so we have a level of confidence that we’re not doing our customers a disservice. In addition, we don’t want to send a mixed message by providing code that goes against some of our own published (and followed) best practices (like not using private APIs). I know the historical Sysinternals members can overlook this, but I’m driven by a baseline that includes our entire customer base that may not be familiar with these tools or their history.

    3) Our resources are tapped out trying to get this site up and will be for the next couple months. Right now my driver is the 600,000 daily visits to the site and trying to ease that transition experience. In addition, Mark and Bryce are revving bits, sometimes several times a day, which are fixing bugs and issues as they flow in from this new launch. Adding un-scoped features like source code is not at the top of my agenda right now. Getting a better understanding of the source code usage scenarios would help me elevate it.

    I’m asking you to work with me on this, not against me.</blockquote>

    Sounds perfectly reasonable to me. Many commenters here seem to think the old sysinternals site was some kind of ‘beacon’ within the open source community. It wasn’t. Mark was always selective in the source code he provided, and that is also perfectly reasonable. Far, far too many people are jumping on the anti-MS bandwagon without stopping to consider where they are *really* coming from.

    Read point 2 from Ottoh above. If MS were to publish the source code they would have to put it through all kinds of rigorous tests first. They would potentially have to review hundreds of pages of documentation on coding practices and style guidelines and modify the source to bring it in line. This would inevitably damage its individuality and independence, not to mention raising issues about who does the modifying. (Should it be Mark and Bryce, or MS employees, or both? How would that work? And what effect would it have on their relationship?) Everything has to be reviewed and double checked to make sure they are not giving out mixed messages or going against policy, and all of this requires resources. That is the way beaurocracy in a large corporation works – somebody has to justify it to somebody above them, who then in turn has to justify it to the people who control the budget etc. There is much more to it than simply "uploading them to a microsoft download server and posting a link to it".

    Yes there is a community here, but MS is a business. Winternals is and always was a business. Sysinternals was created to provide some smaller yet powerful utilities to developers and administrators free of charge. <i>Some</i> source code was included. That’s all. If we want the source code back, we should be making the business case for it, not slagging MS off for the sake of it.

    If I were Mark I would feel thoroughly disillusioned by many of the comments above – they would make me wonder if my readers had ever really understood me at all.

  70. asd says:

    yes, great, another guy who doesn’t stop and try to think outside the corporate frame.

    little question: ever heard of providing software/source-code "AS-IS"? it is possible to publish things without any obligations or needs for changes at all, but they willingly chose to ignore this option for reasons that are all too obvious.

  71. anonymous says:

    Seems like someone sold out again.

    I guess everybody’s human after all,

    everybody has a price 😛

    I’m so sad to see an independent site go.

  72. AngryBrit says:

    "yes, great, another guy who doesn’t stop and try to think outside the corporate frame.

    little question: ever heard of providing software/source-code "AS-IS"? it is possible to publish things without any obligations or needs for changes at all, but they willingly chose to ignore this option for reasons that are all too obvious."

    As I pointed out above, the original sysinternals site did not provide the source code for every utility. Notable by their absence were Process Explorer, PageDefrag and many others (basically all the advanced utilities – the ones you really *want* to get your hands on). You’re acting like there has been a major departure from what went before, and that simply isn’t the case.

    I am a developer, and for me the most valuable thing by far on the old site was Mark’s blog. If that were to go I’d be gutted. The source code I’m not really too bothered about. If I want to do something, I’ll write it myself. If I need more insight into how Windows works, I’ll buy Mark’s book "Windows Internals" – it’s been on my list of books to get for months now.

  73. ert says:

    "You’re acting like there has been a major departure from what went before, and that simply isn’t the case."

    That’s not true. Mark and Bryce are famous for demonstrating how to use several undocumented features of windows. There where several articles and accompanying source code that dealt with and showed how to use these features on the old site. Those are now all gone. That’s a major policy change. An expected change since MS now owns the site, but a major change nonetheless.

    And for the future, one can’t help but wonder if they are free to publish any new findings now that MS signs their paycheques.

  74. db90h says:

    May of the source codes demonstrate use of APIs that can be scarcefound elsewhere, even in Mark’s book. Sure, some of this information might be misused – but surely nobody really believes in ‘security through obscurity’. This is just an excuse, we all know that.

    The simple fact of the matter is that corporations are about profit, not availability of source codes. THIS is the fundamental change that took place when sysinternal’s was bought up.

    Want the source codes back? Prove to Microsoft that they can profit more by providing them than by not doing so. That is the only argument they understand – all else is meaningless to them. They have proven this over and over again.

  75. JamesFrost says:

    I’m in two minds (at least) about this whole affair. Sysinternals has been one of the best provider of tools for IS staff out there, especially regmon, filemon and pstools. The fact that the tools have always been free of charge is pretty incredible, and I always wondered how they made money.

    I am sad that MS have bought sysinternals, but I’m not really sure why. The new process monitor tool is fantastic, but I’m nervous about the licensing changes. The lack of source code bothers me, but I’ve never looked at it before (and it was not for all products anyway) so is it really an issue? I’m not sure.

    My only real comment is to thank Mark for producing a great set of tools, and good luck to him for getting Microsoft to buy them. I do hope the change is good for the community, but whichever way it ends up going we have been better off having sysinternals to play with.

    If Microsoft do manage to stuff it up somehow, then there is always the option of the community getting together to produce the next great open source toolkit, rather than complaining about corporate politics.

  76. Anthony says:

    Hi Otto,

    Thank you for taking the time to address the issue many have had over the source code.

    I am having trouble understanding why you just cannot have a link to the old stuff with a disclaimer to use at your own risk? All the reasons why you cannot keep up the changes can be listed along with the disclaimer.

    The code and developer information (I could not find the developer information section) was just a handy thing to have access to when a developer such as myself was/is working with a related code.

    As a developer, I now know that I cannot turn to this website for information anymore. If this is Microsoft’s intention, they have succeeded. This may not make much sense to you if you are not a developer.

  77. a former admirer says:

    Well,

    as sure as this thread is been watched, it will be the last sequence of long enthusiastic development which was appreciated by many people dealing with everyday problems in the world of today and tomorrow. can’t blame mark – he’s done a remarkable job over the time and may go on to the next level.

    For all those people which liked lemmings and have been working with the sysinternal-tools – farewell with a tear in the eyes loosing one more of the few good sites on the web.

    cu

  78. Bob says:

    Why not just put the source code up for some period of time (till the end of the year) and end all these complaints?? I think the fact that now that it is gone when a lot of people thought it would continue to be there as was originally promised/implied is what’s riling so many people?? This is such an easy problem to solve, I can’t believe Ottoh or Mark or someone with juice doesn’t do something to stop all the bad feelings this is causing. Anyone who cares and doesn’t know about the problem by now likely doesn’t care. How many complaints do you need to think that this is not a valid point?? Please bring back the source code for a time and give us a chance to do what we should have done already.

    And hope that people learn something and keep this in mind for the future. Any tool that you find valuable, download it and save it for a rainy day. Thats why they make such large drives nowadays at such good prices.

    Thanks for listening.

  79. Borgna Marco says:

    SysInternals has never been opensource.  Only small source code chunk where available. As a sample the "File Monitor" utility it’s using some "dirty trick" never shown.

    Ms is just extending the SysInternals tradition.

  80. dev/null [hDs] says:

    so …

    a month ago and earlier the source code was good enough, but now magically its bad?

    only thing what changed was the owner…

    so, the source code will not run/compile on Vista?

    then … i’m wondering it will be the case for binary versions

    also what has someone before pointed out, why the binary size of some tools have raised by 3x ?

    many questions and i predict no real answer.

    i also wonder Ottoh, who are you? An MS employee? maybe the new ‘boss’ of Mark?

    … so many questions… ;|

  81. Jeff Cross says:

    When the Sysinternals acquisition was announced, the boards were full of conspiracy theories of how Microsoft just wanted to censor Sysinternals and hide everything they found embarrassing (even information which is critical for us users).  I actually defended MS, and for that I now feel like an idiot.  In removing the source code (and several of the tools), MS did exactly what the conspiracy theorists predicted.  You can put the source code back up (and I hope you do), but neither MS nor the new Sysinternals can ever regain my trust.  I hope Mark and Bryce at least made a pretty penny when they sold out.

  82. KLC says:

    OK SO HERE’S THE SCOOP!

    THEY HAVE NOW HEARD HOW WE ALL FEEL.

    DO THEY CARE ? NO

    DO WE, MOSTLY DEVELOPERS AND IT FOLKS, REALLY MATTER TO THEM? NO

    WILL THEY SCREW THEIR BEST SOURCE OF PROLIFERATION? YES

    WERE ALL THESE COMMENTS POINTLESS? YES

    DID THESE COMMENTS FALL ON DEAF EARS? YES

    HAVE YOU NOW CREATED MORE ANIMOSITY BY ONE’S YOU NEED THE MOST? YES

    DID YOU LIE? ABSOLUTELY

    JUST WAIT AND SEE.

    REMEMBER "THE BOY WHO CRIED WOLF"

    ONE DAY YOU’LL REALLY NEED US!

  83. mcc says:

    Well, I am as quite a big number of persons VERY disappointed by this decision to remove source code. And even more disappointed by the bullshit explanation given. This is really calling us idiots….

    Sources were sources of TOOLS and more than that, adavnced troubleshooting tools. We ALL know these could be not as clean as samples provided by MSDN, but the usage is different. And people using them are also different.

    Just put some legal coments or whatever if you are afraid of people using parts on production apps, but put the source back. It was very valuable, enabling us to modify some of the tools for specific usage, and fixing some of the issues. It also enabled us to learn.

    I am one of the (few) pro-MS guys, but here you are really giving good reasons to hate you and to call you liars.

    And in this case, well, I am really on THEIR side….

  84. Norman Diamond says:

    Mr. Helweg, I own a BOOK which says on page xxix:

    > Updates and corrections will be posted on the

    > page http://www.sysinternals.com/windowsinternals

    Can you guess who the PUBLISHER and authors and title of the book might be?

    Why does that URL yield an HTML error 404?

    If I make an adjustment to

    http://www.sysinternals.com/windowsinternals.html

    why does it yield a page in which updates and corrections have been deleted?

    Mr. Helweg can you talk to the book’s PUBLISHER about getting that site reinstated and/or migrated?

    As for publication of source code, as others have said, writers of malware already have it.  Writers of malware also had the source code to the predecessor of Windows NT, i.e. VMS.  Only legitimate developers couldn’t get the source code.

    Now I DO understand that some of the source code published by SysInternals didn’t match Microsoft’s standards.  I reported one whole bug to Mr. Russinovich.  His source code was maybe only 100 times more reliable than source code examples that are published in MSDN or downloadable in some Microsoft SDKs.  Please do not adjust the quality to Microsoft’s standard.  Please reinstate the source code as it was.

    Sure the number of downloads of source code was less than the number of downloads of binaries.  The number of programmers is smaller than the number of users.  Even programmers are users and don’t always download sources of tools that they use.

  85. dvl says:

    Oh my, it’s a good material for a movie like Antitrust. Sources are still available on p2p networks (some of  packages are even marked as sysinternals_pre-microsoft). By trying to hide them MS only contributed to their underground distribution.

  86. wch says:

    Just one more vote calling BS.  MS:  read the news – Sun finally saw the light the other day, about 3 years too late.  It may be difficult to open the source for large MS products due to 3rd party restrictions, politics and inertia, but CLOSING the source on a new acquisition is inexcusable.

    We all use linux; sysinternals utilities made the rest of our jobs bearable, and now we can’t even trust those.

    SysInternals NewSID v4.10 is 112KB, source available.

    Microsoft NewSID v4.10 is is 223KB, source withheld.

    Does the new EULA really take up 111KB?  Can you be sure?  Will Vista even support cloning?  Will I care?

  87. James Dennis says:

    "I maintain that the current source code decision is driven more by resources and priorities than it is about policy."

    However it seems that it is the MS policy

    requirements that need 99% of the resources necessarily to get the source published.

    I ended up at this blog post today because I needed some source code – specifically FMIFS as it seems there is no "official" API for formatting a drive without showing UI.

    I’m sure that the lack of publication of this API was done for "security" reasons before MS started to take security seriously as hiding this API makes life harder just for the professionals. A malware writer won’t care about formatting a drive into nice cluster sizes, they will just overwrite with garbage.

    I may be wrong on this assumption but two things are fact:

    1) I require access to this undocumented API to continue (or I need to implement a format from scratch).

    2) Now, due to microsoft policies, it is no longer available.

  88. Bob Dean says:

    As of 2006-11-17… FMIFS source code is still available… check out:

    http://www.sysinternals.com/SourceCode/fmifs.html

    You can see other (although, probably not complete) sysinternals source code files by navigating to:

    http://www.sysinternals.com/SourceCode.html

    Hope this helps :-)

  89. John Smith says:

    > Wednesday, November 15, 2006 5:04 AM by Jeff Cross

    > … I hope Mark and Bryce at least made a pretty penny when they sold out.

    Well, that’s easy to find out – the following is an excerpt from MS SEC Filing (From 10-Q), dated October 26, 2006:

    "During the three months ended September 30, 2006, we recorded goodwill resulting from the following acquisitions: …; Winternals Software LP ($31 million); and others … All of the entities were consolidated with Microsoft since their respective acquisition dates. The purchase price allocations for these acquisitions are preliminary and subject to revision as more detailed analyses are completed and additional information about fair value of assets and liabilities becomes available."

    Congratulations to Mark and Bryce!

  90. Paul says:

    My thanks to SysInternals for their dedication in making Windows a better product.

  91. Johh M. says:

    I just can’t believe it, but actually, I knew it somehow. That’s why I downloaded everything when the transition news came. I had a hunch MS would remove sources. Shame on you, AGAIN.

  92. r-mi says:

    So it means its the end of sysinternals innovation and users will get typical "microsoft style" utilities instead – crappy and designed for morons. And of course you remove the sourcecode – how nice.

    I think that going from domain to this technet crap was very bad decision. Maybe good to promote technet. Who uses technet anyways?

  93. David says:

    Ryan, do you know where I can find the latest source code version of Filemon?

  94. Eric says:

    The source code was one of the most vital and useful parts of sysinternals.com to me.  I have learned more about various windows programming topics here than anywhere else.

    PLEASE bring the source code back and continue to add to it.  It’s such a valuable learning tool!

  95. Farid says:

    At least, the sources are still archived at the usual places… AND they’re available on p2p networks too. By NOT offering them on microsoft.com, you’re actually indirectly and perhaps unintentionally contributing to spreading malware (who knows if all those tar balls/zips don’t contain *modified* source?).

    If you have problems with adding the source code files here (for now?), PLEASE at least post their original MD5 and SHA1 checksums, so we can verify the integrity of the source zips floating around.

  96. Adam says:

    Yes it’s changed surprise, surprise! Instead of bitching about it I chose to download all samples from the old site that the kind poster took the time to find. I would advise doing the same! Mark and Bryce moving to MS makes perfect sense, They’ve spent years reversing windows components to get a better understanding of them and developed some awesome tools along the way to help them which they have kindly shared with the world. Now that they are inside MS I would think a lot of their reversing work got a lot easier. Instead of having to tediously reverse something to find out how it works they can probably access documentation on it or even speak to the developer of it. Don’t give them a hard time over this try and think about what they have contributed so far and be grateful for that. I certainly am! I would like to see the source on the site, more free tools and the source to those tools but I don’t think it’s going to happen so I’d just like to say a BIG thanks to them for all they’ve done up to this point. And wish them both the best wishes for there futures!

  97. Miguel Pérez says:

    So SysInternals is now part of Microsoft. I don’t mind where it is as long as it’s kept to what it is: a great technical resource full of all sorts of utilities that deal with the internals of Windows.

    I just don’t want anything to be removed, and I don’t want this to turn into a "scale your profits and lower your TCO by optimizing the cash flow of" bizbabble. Keep it 100% technical, keep the marketing and business guys far, very far from it, and SysInternals will keep being very useful for people doing the real work here.

  98. Miguel Pérez says:

    Oh, now I read "not being migrated". It looks like I was too quick to post my comment that I don’t mind.

    Man. This is so Microsoft-ly. Well I guess we can say bye bye to another great technical resource. My image of Microsoft went down once again and must be now at sub-zero levels. Not only Microsoft is closed, greedy and not developer friendly – it’s also purposefully developer unfriendly, buying things out just to close the source.

    This is yet another reminder of my decision to migrate to Linux as Windows DRM Edition (Windows Vista) is out – both personally and professionally. Open source communities aren’t evil, while Microsoft keeps focusing their efforts on making my life ugly and siding with anybody but their customers. Way to go.

  99. AngryBrit says:

    "Open source communities aren’t evil, while Microsoft keeps focusing their efforts on making my life ugly and siding with anybody but their customers. Way to go."

    Open source communities do not make up the majority of Microsoft’s customer base. When you say "siding with anybody but their customers" what you really mean is "siding with anybody but the open source community". Not the same thing at all.

  100. Miguel Pérez says:

    "When you say "siding with anybody but their customers" what you really mean is "siding with anybody but the open source community"."

    First, by closing the source of these utilities I don’t understand who are they siding with other than themselves, while some of the open source community are still Microsoft customers. Second, they also side with media corporations and bundle malware with their OSes and media players which they sell to their customers. Talk about customer betrayal.

  101. AngryBrit says:

    Microsoft has millions of customers worldwide who depend on their products day in day out, whether that is its operating systems, office applications, development tools or whatever.

    In order to maintain that level of commitment and integrity, high level policies (such as not providing source code to developers without vetting it first) have to be strictly adhered to. Occasionally there will be circumstances where that decision doesn’t seem to make much sense. It doesn’t mean there is a conspiracy.

  102. Paul Evans says:

    The source code often showed "best practice" type behaviour, and often demostrated things that were not terribly well documented to the public.

    Please consider putting the source code on CodePlex or similar and keep access to such a rich and educational resource open.

  103. Resigned 2 Inevitable says:

    Glad to see the forefathers of Sysinternals cashed in.  Not glad to see MS take possession of this resource.  Stop grousing about the disappearing source code and debate when none of the tools will install without the Genuine Windows Advantage lock on the door.

    What if, this move actually decreased the value of Windows just a tad – a reliable sophisticated non-Microsoft resource concerning Windows goes away. "Not going away" doth protest Otto and/or Mark – at least until internal consensus develops over how to monetize it.

    Ah well it’s always a good thing to encourage competition and give Ubuntu et al more reasons to live.

  104. deejayy says:

    i’m planning to mirror all binaries and source codes from the old sysinternals.com. is it legal to publish a tar.gz of all of these stuff?

  105. Norman Diamond says:

    > is it legal to publish a tar.gz of all of

    > these stuff?

    In countries that obey copyright treaties the answer is no.  You can make copies for yourself, or you can give someone else the copies that you downloaded if you don’t keep any copies for yourself, but you can’t make and distribute further copies.

  106. Yuhong Bao says:

    Some of the things on the Sysinternals site, such as the article "Inside Native Applications" and source code, are more appoperate for MSDN anyway.

  107. colombian user says:

    oh my God!

    how is possible not to migrate the source code?

    we really must have them….

    PLEASE MARK, can you do something about?

  108. andy says:

    mark you have been sold out

    its true everyone has a price

  109. Matt says:

    Ouch!

    Bring back the source code guys.  We all now your excuse is utterly pitiful and meaningless.

    MS strikes again.

    Down pesky ants!  Down!

    <stomp> <stomp>

    How can you possibly know more about our OS than we do!

    <stomp> <stomp>

    Imagine all the incredible software advances that have been pulverized by this software giant just so it can stay on top of everyone else.  It is like the mythical 100 mile per gallon car engine.  People claimed they saw and then poof Detroit made it disappear.

    Capitalism at its best I suppose.

  110. mike Rose says:

    secret has never avoided security’s holes.

    M$ security holes are numberous and widespread.

    So many patchs, so many buggy programs.

    IT administrators, you must resist :

    Boycott M$ products, don’t migrate as long as you can.

  111. Brian says:

    What made sysinternals nice is that their software did things that the MS versions did not do or even acknowledge that one could do (or see).   Instead of modifing the MS versions, which was well within their capabilities, MS buys out SI.   My big problem is the loss of the source code and the new EULA.   The EULA prohibits reverse engineering of the code, and prohibits modification to "work around technical limitations"

    What MS did is embrace and extend.   The original SI software did things that MS didn’t want you to do.   Now future SI software will not do those unwanted things, and we will be powerless (legally) to do anything about it.

    The whole benefit of using SI software will soon be eliminated.

    Danm.

  112. Brian says:

    Just wanted to add a thank you to you guys.   Your tools have been/are the most powerful, useful, and irreplaceable tools for software developers on the windows platform, and IT professionals trying to debug strange issues.

    Congradulations and good luck on your future endeavours!   I just hope someone is willing/able to pick up the newly formed slack!

  113. A poor little peon who likes source code says:

    Good sirs and maddams, if you wish for the source code go to http://www.archive.org, type in "www.sysinternals.com" to go "back" to the old page where you can download archived copies of all the sources. I’m not sure they’re the latest but it’s better than nothing.

  114. A poor little peon who likes source code says:

    Oops I almost forgot – Merry Christmas!!!!

  115. A poor little peon who likes source code says:

    And at the risk of spamming this blog’s comments – I now offer you my 15 minutes’ work of collecting all the source codes (and info pages for each tool) using http://www.archive.org:

    http://www.megaupload.com/?d=H25RWTHC

  116. A poor little peon who likes source code says:

    And at the risk of spamming this blog’s comments – I now offer you my 15 minutes’ work of collecting all the source codes (and info pages for each tool) using http://www.archive.org:

    http://www.megaupload.com/?d=H25RWTHC

  117. annonymus says:

    What a truely sad day this must have been.

    Migrateing to MS suprevision what a low and disgracefull way to earn more money.

    your SC excuses are pityfull and redicule, MS dont like OpenSources thats a fact. sad now i have to migrate to, Any recommendations on other projects similar to Sysinternals previous work are welcome!.

    GL chocking on the $

  118. John says:

    Haha "search online" in autoruns goes to MS live search now…

    You guys are like Nazis!

  119. Bob says:

    Come on people, play fair. The situation appears to be thus:

    Mark et al sold their stuff to M$. Good for them, I say, they made some money out of what they did for us for a long time. The tools we’ve had have been invaluable, and must have taken a lot of time and effort. I’m glad that they’ve received some just rewards for their efforts.

    Now, M$ haven’t migrated the source code. Why? Well, it seems that if M$ take and publish the source, M$ is signing off on it. This isn’t good for them, as it would require a LOT of checking. So they won’t bother and hence the source is not available from M$. Hopefully some workaround might be possible in which the source is provided "as is" or something, on the understanding that it is not M$ endorsed. But give Mark a break here – we’ve had great stuff, and now he’s getting money for it. Be happy for the man!

  120. Chris says:

    Congrats Mark & Bryce – I hope you guys are getting a well-earned rest and enjoying the fruits of your labour.

    Shame on you Microsoft – with Virtualization features appearing on every new Intel and AMD processor, you can expect me to be doing a little migration myself for our next generation product. You manage to devalue Windows just when you least need it commoditized. Good luck with Vista – you’re going to need it!

  121. Vince P says:

    You people sound like a bunch of a Rosie O’Donnells. You dont own the source code, you should be grateful that it was being shared to the public for as long as it was.  And besides if you cared so much about it, you would have already downloaded it.

     Idiots.

  122. Rogerborg says:

    Thanks, peon, much appreciated.

  123. conniechoochoo says:

    Hi there 

    By the way, I love that too!  How did you find that?  

    Bye, – MyGirl! 

    [color=#99aadd][url=http://paid-review-site-surveyihrjnp.blogspot.com]see how I make free money with paid online surveys[/url][/color]

  124. Merk says:

    Given MS’ total inability to properly document ANY of their own API’s and their subsequent destruction of this primary source of knowledge in that area, there is little reason to pursue any further development on the MS platform.  

    They can’t migrate the source code?  Migrate it how?  To VB?  Don’t make me laugh.  The code they post on MSDN is trivial, misleading, and usually won’t even compile.  In short, the source they already publish is garbage.  The legacy Sysinternals code is eons ahead of MS code in every area.  MS has NO coding standards.  Ask them when they plan to complete their initial CMMI appraisal.  ISO 9001?  ANYTHING?

    They don’t want anyone but themselves to develop on Windows, and I for one think it’s time to let them get their wish.  If they really want to quash all independent development, so be it and let them live with the consequences.  The independent developers were the only people advancing the state of art for MS products.  Killing off their sole remaining source of innovation can only help accelerate their decline and fall.  

    I am down to one Windows machine, all the other boxes in my house have long been "migrated" to OS X or Linux.  I will NOT be loading Vista or buying any more MS products of any kind — ever — and I will continue to promote the  adoption of open standards, systems, and software in all my IT projects.  

  125. ... says:

    The information I found here was rather helpful. Thank you for this.

  126. fedellisaz says:

    Biggest site for you

    http://www.stormwarez.info

    [URL]http://stormwarez.info[/URL]

  127. Automoiles says:

    stiller!lured affiliate outvotes superstitious.provable escaped pupil economize

    http://www.mikepelchy.com/##-provident-plc- periodical cartoon Romanizes locker,McFarland
    http://www.ctcfn.com/##-North-Carolina- astray,rattler?beseech

    http://www.stateofbliss.co.uk/##-rate-comparison- glees peddlers!Holmes nondescript
    http://www.ti2xguher.com/##-ga__- rumbles?ensued silkier domesticating
    http://www.marioboccardo.com/##-plan- costs separations
    http://www.wltk.net/##-united-company- assimilated profile?investor buns!enter
    http://www.innafridman.biz/##-general- retyping Stetsons

  128. ... says:

    Luogo molto buon:) Buona fortuna!

  129. ... says:

    E evidente che il luogo e stato fatto dalla persona che realmente conosce il mestiere!

  130. ... says:

    Lo trovo piuttosto impressionante. Lavoro grande fatto..)

  131. Britneyoizbq says:

    Very nice! I have some LJ with news, check this out:

    <a href= http://iwantubadlyz.livejournal.com >Newest news</a>

    <a href= http://annakubat.livejournal.com >Check this out</a>

    <a href= http://jackie_simpson.livejournal.com >livejournal</a>

  132. ... says:

    Interessieren. SEHR interessant! 😉

  133. ... says:

    pagine piuttosto informative, piacevoli =)

  134. aarst says:

    higuys!What yourblog powered by?

  135. aarst says:

    higuys!What yourblog powered by?