New version today will NOT install on one PC?
When I booted today I got the notice of the new version. My PC was able to install it with NO problem.
My wife booted her PC and it will NOT install. Screen goes blue tint and W10 Creator versions (same as I have) puts up this dialog box:
=======
This app had been blocked by your System Administrator
=======
Says see Administrator to fix this.
Well she (and I) are running as Administrator. The icon on both of our PC's have the blue/gold shields which does mean they are running as Administrator. I went into her UAC and turned it completely off (hers is on the Default, mine is OFF) but that didn't help.
I looked at the icon Properties and noticed she had TWO that seemed odd. One was Administrator and the other was Administrators??? The Administrator one had a red X? It had only Special Permissions. Hmm, that was odd too. Then looked at my PC, same thing?
See attached file?
Why the difference and she can't install it?
Attachment | Size |
---|---|
capture.jpg | 44.98 KB |

- Log in to post comments

Thanks. That worked... wonder why?
I did check some more... could be a few things.
Although our PC's are 'similar' they are not in terms of the Window10 Install. Her PC started life as a Win7 Pro x64 and mine a Win8 Home x64.
I've searched the web and that dialog box is common since late 2015 on Win8 and Win10 Pro PC's. Some point to AppLocker as the cause. However that is NOT part of Win8 or Win10 Pro. Oddly enough wife's PC does have an APPLOCKER folder, but it is EMPTY. Suspect some hidden AppLocker settings are the culprit here. Something might be set from prior versions that caused the install to fail...
I also noticed that we have real difference settings in Windows Defender. I've got the AV and FW OFF, hers are one. She's using Norton's ISS, and I've got McAfee's LiveSafe.... I don't think this has anything to do with it though?
- Log in to post comments

Possibly - AV programs have been known to block downloads - especially if they have their own firewalls. Personally, I just grab the main downloader and run it to be on the safe side. Overall, I think it helps ensure that the download is successful and then I know I have the full file (which can be used again to run a repair install if need be down the road too).
Overtime upgrades bring their own share of issues. I had a fress Win 10 1607 install and the creator's update borked up my user profile - kept having all kinds of weird issues. Created a new user profile and copied my data over and no more weird issues. So we have Windows OS upgrade issues, compounded with Acronis version upgrade issues... some people have no trouble, others, do.
Glad that the full installer download and run allowed things to work for you though! FYI, when running any installers in Windows 10, get used to right-clicking and "run as administrator" even if you're logged in with an admin account. That's the only way to get full admin access for the installer process and it may be the difference between a good or bad experience with the application once it has been installed.
- Log in to post comments

Bobbo, thanks for the reply.
If the A/V (Norton Internet Security Suite) was troublesome I'd think it would have been for all attempts. Should be the same file, no?
I'll usually not bother running d/l's via the Administrator. Only switch to that when they fail for some reason. Did think about running as Administrator even though it was showing the shield but didn't.
However since one PC was OK and not the other, that confused me. I started looking for 'difference' in the setups for reasons why? Never had other 'odd' problems with that PC before so I targeted the problem as with MS's Creator update.
I 'pushed' Creator on my PC (technically advanced and I don't mind taking chances and restoring a backup) and it FAILED the first time. Seems when I tried again I got a prompt for some 'permissions' fixes I didn't see (or get) the first time. After that is processed fine on my PC. I did have Dell Audio problems as it was out of whack and way too low. Nothing else that I recall.
Wife's PC processed smooth. Then the Acronis problem. We did have a sort of serious problem before that with the Network.
She has 2 wireless devices, on on-board Intel N speed card and a Netgear USB AC speed dongle. She had ALWAYS run on the AC adapter. So I could easily FTP to her PC I set the IP Address to be 192.168.1.30 and mine is 192.168.1.40. Easier for her to move files from one PC to the other. Well Creator messed that up ROYALY. It made her N speed WIFI and the AC WIFI2. It enabled WIFI and disabled WIFI2. Wife did mention that her PC seemed slower and I didn't really see that. One day I had been printing to our Wireless Printer before her PC was on. It has a fixed IP Address of 192.168.1.10. I've set the router to issue our PC address via a MAC reserved address. Wireless devices could only be enabled up to .8. Later after she turned on her PC I discovered I could no longer print. An HP and did the usual, ran HP Dr. It said it couldn't find the printer, I entered the address manually and it still couldn't. Wife said send her what I wanted to print. Now she couldn't either. HP Dr. couldn't help on her PC either? OK, did the IPCONFIG /flush and /renew. Only then when I ran IPCONFIG /ALL did I see that she was on N speed device AND her IP Address was 192.168.1.10... which knocked the printer off-line!!! I tried setting the MAC address to be something else, no matter what I did, I couldn't move the PC off of that IP Address... reboots, disable and enabled the adapter, power off and on, no help. So I moved the printer to a different address and that fixed the problem. 2 days later I enabled the N device, it got the IP Address that the MAC address was to get? I don't know why it did then???
It seems no MS has changed its tune on getting Creator, see https://www.infopackets.com/news/10087/microsoft-dont-jump-gun-windows-10-update, at least for manually getting it. I assume they can tell what to update based on H/W?
- Log in to post comments