Thanks @stapp and @Krusty13 , downloaded the portable version and will try it as per @stapp instruction later today (I have to do some office stuff at first). In the meantime @Phant0m maybe will bring another idea.
That repair can only cover what it was programmed to-do. It doesn't look like Store-App cases is one of them.
I had a different issue with the Photos app. It was working fine, but I wanted to use Honeyview to view pictures instead, as I had done with the previous build of Windows 10. I was not able to change it from Default app settings - when I selected Honeyview, Photos stayed as the default. However I was able to change it with the right click context menu. I selected Open with/Choose another app, selected Honeyview and chchked Always use this app to open .jpg files. On an unrelated issue, the upgrade to Windows 10 AU has failed twice on a second laptop when using the Windows10Upgrade exe. There was no error message, the upgraded didn't complete and rolled back to the previous build. I'm pretty sure I had shut down my antivirus the first time, and I made sure it was shut down the second time. I'm trying a third time with an ISO downloaded using the Media Creation Tool. I wrote the ISO to a flash drive with Rufus. I figured it would upgrade with no issues as this computer does not get used much, does not have much software installed and has no problems installing Windows Updates. The laptop I was able to upgrade to Windows 10 is well used and has hundreds of programs installed, and refused to install updates.
roger_m not sufficient enough to simply shut down the AV before starting. For instances, AVG is a known case to me where the drivers needs to be disabled from starting. Because Windows could be on the last stage and at 99% and fail and roll-back because of the AVG drivers. You want to temporarily disable AV components from starting with windows, and make sure you disable them drivers also.
Thanks for your suggestion sent via PM but it didn't help neither. :-( EDIT: Seeing troubles of other folks to even successfully upgrade or facing severe issues afterwards, my issue with Photos is simply nothing and you don't need to waste your time with it.
Are kernel mode drivers need to be signed by MS? I have several win 8.1 drivers obtained from hp website installed in win 10. I have not yet installed the AU. If they don't work I have to disable secure boot but I will loose security. I am thinking of going back to windows 8.1.
What is installed in current WIN10 will work in AU (EV signed or not). But if you happen to remove them before updating AU you may have difficulties to re-install them after the AU.
I'll give that a try. The upgrade is failing when installing updates. When I used the ISO to upgrade, it failed with error 0xc1900101 0x40017.
Yes, I did that. I just ran a SFC /scannow and it found and fixed some problems. I rebooted and am trying the upgrade again.
I did a clean install of the AU as I was having to many problems with the live over the top attempts...Now this new driver blocking is driving me mad, MBAE doesn't install properly, Voodoshield also fails...Back to 1511 until this is sorted out...One very unhappy customer.
Re Voodooshield, perhaps this applied to you clubhouse1 ? https://www.wilderssecurity.com/threads/voodooshield.313706/page-469#post-2606242
I could install an older version of VoodooShield ( 3.08 ) without problems after a clean install of the AU. And stopped working today
Could EAM still be used as a companion antivirus? - Emsisoft Anti-Malware - Emsisoft Support Forums "The thing with compatibility is that it outright blocks a whole bunch of features we would like to add. That is why we no longer recommend using EAM alongside any other AV software. At the moment we are still compatible with pretty much all of them and if we can easily work around a conflict we will still do so. However, we no longer consider a degradation of compatibility a blocker for new features."Posted 14 November 2015
We're not talking about conflicting AVs here. We're talking about Microsoft blocking companion AM tools like EAM. I mean... is taking consumer choice as well as user control away over Windows part of what Microsoft wants to do with Windows 10? None of this was a problem in earlier versions of Windows.
I had MBAE installed, but not running, when I upgraded and turned it back on after the upgrade. It appears to be running when turned back on.
I sucessfully installed the upgrade and everything seemed fine. However I then decided to try O&O ShutUp10 which I have never used before. I only selected the green ticked recommended items to try first and after about an hour my PC suddenly shut itself down for no known reason. I rebooted and it worked fine for about another hour but then shut itself down again. I then decided to untick the items and so far my computer has run fine with no further shut downs. So is it possible that the current version of O&O ShutUp10 is not compatible with the AU and could this be the reason for these shut downs which I never experienced before on my PC which is often left on all day long with no problems. I'm wondering if the various changes to how things like Cortana have been implemented to prevent it being disabled could in some way force a shut down when the utility is trying to do something that is no longer permitted.
@zarzenz It's hard to say if O&O caused the shutdown issue, however, you should probably not have installed the existing version of Shutup10 until O&O has had time to put out a new version that handles everything in this new Win 10 Anniversary Update. I've also noticed on Win 10 1511 that once you run Shutup10, you really can't go back to the Win 10 defaults anymore, even though it looks like you can. I found that some settings were not reset to defaults and then realized that once you commit to running Shutup10, that's it. I would have waited for a new version specifically made for the AU edition of 10.
Thank you Kerodo and what you say makes perfect sense. I think the reason I did it was because on my original upgrade I followed the steps given in the fix10.isleaked site and I thought ShutUp10 would be a simpler way to tighten up the privacy side of things. I'm pleased to say that since reverting back to the default state even if some of the settings haven't reverted, it does seem to have fixed the shut down issue. What I may even do now is just out of interest tick one at a time back on to see if I can isolate which setting is responsible for the shut down. I will then know for sure that is was ShutUp10 that caused the problem and will then wait for any new version to be released for the permanent fixes to be applied. I was very impressed with the interface and the simplicity of this utility and hope it can be updated soon to address the new conditions in the AU.
Thanks for the heads up, I missed that..I'll wait a few weeks until the developers have had a chance to catch up rather than disable secure boot
Hi Norman F If your question was directed at me, when I turned my AM (EMIS 11) back on after upgrading to Win 1067, WD RealTime was turned off.
Well, I went ahead and created an Outlook account, signed in to Store, dodged syncing it the machine login so I was only logged into Store, installed AdBlock Plus and LastPass. Before I had even selected the three options you see on the first-run page of ABP that shows I get a message saying the Subscriptions were full and to remove some. I did not. I closed Edge, ran CCleaner and restarted my machine, opened Edge and I'm not seeing that message now (or for now).