Changes to bcdedit.exe access, or am I having BCD issues?

I'm running Win10 Pro x64 1607. I have a bunch of command scripts that check for elevation with the following line:

Code:

for /f "tokens=1,2*" %%a in ('%SystemRoot%\System32\bcdedit.exe') do if (%%a)==(Access) goto :NoAdmin

Starting about a day ago, all the applicable scripts started going to ":NoAdmin" due to the fact that bcdedit.exe was denying access (and instead issuing an "Access is denied" reply). This happens even if I am using a command window that is elevated:

Code:

C:\Temp>%SystemRoot%\System32\bcdedit.exe
The boot configuration data store could not be opened.Access is denied.

Was this due to a recent update? I can't find info on it if it is. I can use another means of detecting elevation, but I want to make sure I'm not just having yet another Win10 issue here.

Sometimes Windows pisses me off so much I just want to use my shotgun on my PC.

Turns out I was having the same issues with DISM, SFC, and probably other native utilities that require elevation. A reboot seems to have "resolved" the issue. (It is not being pedantic to point out that this didn't really "resolve" anything; rather, all it did was work around an issue that obviously still exists.) I guess this is yet another stupid Windows problem.

meh said:

Sometimes Windows pisses me off so much I just want to use my shotgun on my PC.

Turns out I was having the same issues with DISM, SFC, and probably other native utilities that require elevation. A reboot seems to have "resolved" the issue. (It is not being pedantic to point out that this didn't really "resolve" anything; rather, all it did was work around an issue that obviously still exists.) I guess this is yet another stupid Windows problem.

Well if you hadn't logged out after the most recent update (which didn't require a reboot by the way) then your access token may have been out of date for the sessions and administrative access may have been lost. Creating a new one likely "resolved" the issue. I've seen this before.

That would make sense (although not being notified of that condition doesn't make sense), but I logged off and back in yesterday. Looks like the last updates were installed on January 24, which was a week ago.