Windows 10: It Was All Going So Well…

Posted by Viktoria Michaelis on September 26, 2015 in Internet |

I’ve spent the late afternoon today, after my usual half hour getting the computer to work with Windows 10, writing, sending mail and all the things that you do on the Internet. Then, just as I was about to do something new, it crashed. Windows 10 went down the drain again, and this time with a fanfare. The error log which I came across following the crash was five hundred and sixty MB in size. Think about it. 560 MB.

So I went through all the usual things again, rebooting, running ZoneAlarm and getting it back up once more. And, of course, the usual twelve errors showed up. I wonder if anyone at Microsoft will ever get around to solving these problems? I mean, I haven’t blocked the spy mails which go out telling them about performance – well, apart from the 560 MB error report, that’s my bandwidth there! – so something, somewhere is getting the message. Just in case no one is getting the message, and to show others what the problems are, here’s a list:

"C:\Windows\WinSxS\amd64_microsoft-windows-d..-tools-mmc-adsiedit_31bf3856ad364e35_10.0.10240.16384_none_bb26db4c74841a00\ADSIEdit.lnk" broken link to "C:\WINDOWS\system32\adsiedit.msc"


"C:\Windows\WinSxS\amd64_microsoft-windows-d..mc-sitesandservices_31bf3856ad364e35_10.0.10240.16384_none_a73cfa0803f07b5a\Active Directory Sites and Services.lnk" broken link to "C:\WINDOWS\system32\dssite.msc"


"C:\Windows\WinSxS\amd64_microsoft-windows-d..services-computer-setup_31bf3856ad364e35_10.0.10240.16384_none_4425a97518cf0d07\computer Install.lnk" broken link to "C:\WINDOWS\computer\computerinstall.exe"


"C:\Windows\WinSxS\amd64_microsoft-windows-iis-clientshortcuts_31bf3856ad364e35_10.0.10240.16384_none_f1ada44eb15ce85c\IIS Client Manager.lnk" broken link to "C:\WINDOWS\system32\inetsrv\InetMgr.exe"


"C:\Windows\WinSxS\amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.10240.16384_none_892145b64cb3486e\IIS6 Manager.lnk" broken link to "C:\WINDOWS\system32\inetsrv\InetMgr6.exe"


"C:\Windows\WinSxS\amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.10240.16384_none_8fd40f0f55c4c666\IIS Manager.lnk" broken link to "C:\WINDOWS\system32\inetsrv\InetMgr.exe"


"C:\Windows\WinSxS\amd64_microsoft-windows-nfs-adminmmc_31bf3856ad364e35_10.0.10240.16384_none_efb85ae8fe90d90c\Services For Network File System.lnk" broken link to "C:\WINDOWS\system32\nfsmgmt.msc"


"C:\Windows\WinSxS\amd64_microsoft-windows-p..erandprintui-pmcppc_31bf3856ad364e35_10.0.10240.16384_none_1368b39b1b5ef02c\Print Management.lnk" broken link to "C:\WINDOWS\system32\printmanagement.msc"


"C:\Windows\WinSxS\amd64_microsoft-windows-rascmak_31bf3856ad364e35_10.0.10240.16384_none_188cd2401362299a\Connection Manager Administration Kit.lnk" broken link to "C:\Program Files (x86)\CMAK\cmak.exe"


"C:\Windows\WinSxS\amd64_microsoft-windows-s..ment-policytools-ex_31bf3856ad364e35_10.0.10240.16384_none_615fc74cdbc2e977\Security Configuration Management.lnk" broken link to "C:\WINDOWS\system32\secpol.msc"


"C:\Windows\WinSxS\amd64_multipoint-logcollector_31bf3856ad364e35_10.0.10240.16384_none_a822f14b35cf88f8\MultiPoint Log Collector.lnk" broken link to "C:\Program Files (x86)\Windows MultiPoint Server\LogCollector.exe"


"C:\Windows\WinSxS\msil_microsoft-windows-smcsnapin_31bf3856ad364e35_10.0.10240.16384_none_49f122aca3a319df\Scan Management.lnk" broken link to "C:\WINDOWS\system32\ScanManagement.msc"


Since Windows 10, like all the previous versions, is not Open Source and the files are encrypted, I can’t go in there and correct on a permanent basis, not that I would necessarily be brave enough to do it! Perhaps there is someone at Microsoft who knows how these things work and, between coffee breaks, turn their attention to them? I’m sure I wouldn’t be the only one who would be pleased.

  • Viktoria Michaelis.

Tags: , ,


  • Francois says:

    Is your installation clean or was it done over an existing Windows 7 system through the free upgrade?

    The components (listed above) that cause your crashes are things that go boink when you launch something new, a printer for example.
    You have three options for a fix:
    1- Re-install Windows 10 as it seems something went wrong with your initial installation. Note your product key before you download a new ISO file from Microsoft.
    2- Back-up your data and re-install Windows 7. A production machine should not run a new Microsoft OS until Service Pack 1 is released. Mine has two bootable partitions, Win 7 for work, Win 10 for watching it crash.
    3- There are no Service Packs for Windows 10, only constant improvements. However, a major update (a service pack) is coming out in November if you have the patience.
    ZoneAlarm is also my firewall of choice and has been for several years. I would disable it as the modules you list above are involved in connecting to the outside world and ZoneAlarm may be interfering.
    Windows 10 is on its way to being crowned the most unstable MS operating system ever by industry experts. I would re-install Win 7.

    Keep us posted.

    • The installation was done on top of Windows 7 initially, and didn’t work. So I went back to the Windows 7 installation which, thanks to the Windows 10 installation, had been corrupted. I then re-installed Windows 10 through an installation tool rather than the Microsoft direct download, and it worked aside from these 12 connection problems and the fact that each time I delete a file, the registry doesn’t registered the fact that the file is gone. Running ZoneAlarm repairs the errors for long enough so that I can get into the Internet and check my mails. Sometimes it lasts for a few hours!

      I do have enough patience to wait until November, surprisingly enough. There have been quite a few Windows patches so far, and I have had the pleasure of cleaning up my database from what the updates leave over several times.

  • Francois says:

    What I understand from your reply is that you are using the PC Tune Up module of ZoneAlarm to clean your registry database when you get a crash. PC Tune Up might also do other things like empty the recycle bin, get rid of useless temp files, fix broken links (walk the dog, dance the fandango…)

    This could be the problem as few of those utilities collections are Windows 10 compatible. I looked at major entries and only CCleaner by Piriform claims Win 10 support. ZoneAlarm stops at 8.1
    Available from piriform dot com, the free version is enough for most.

    I will run CCleaner now on my Win 10 partition and report on the damage.

  • Erhard says:

    I’ve been a “guinea pig” for MS since Win 98 and have to say that by now I’m fed up with that status. My Win7 machine works flawlessly, so why should I “upgrade” to Win10 right now? The time I’d have to spend on repairing Win10 is lost as my productivity would immensely go down. Upgrade just because it is “free”??? Nope, nothing is “free” in today’s world! I’d rather pay for a reliable and working software than invest my time (the price I’d have to pay for “free”) in finding workarounds for a software’s bugs. In your case (and many other users’), I’d byte the bullet and back up my data, re-install Win7, and go back to a happy work life. Just my 2 cents…
    Good luck,

    • Francois says:

      I completely agree with Erhard: there is no benefit to Windows 10 that is worth this kind of pain (where is the seamless integration across all devices???)

      CCleaner did not emit toxic fumes or attract a plague of frogs, which does not imply it did anything udeful.

  • […] first thing that I noticed after the update was that the twelve irreparable errors I get – connections which do not lead to where they should – are all still there. Not […]

Leave a Reply

Your email address will not be published. Required fields are marked *

Copyright © 2010-2018 Viktoria Michaelis All rights reserved.
This site is using the Desk Mess Mirrored theme, v2.5, from BuyNowShop.com.

error: Content is protected !!