Windows 10: Windows 10 Insider Preview Build 17101 Fast + 17604 Skip Ahead Feb. 14 Insider

Wynona said:

No clues here, Magilla. I still can't boot without WinPE (made with Macrium).

What I also notice is the build will not sleep—when I ‘sleep’ it, it shuts off and is dead. I know it’s not computer, because I can boot into my windows standard partition and sleep it and wake it up. I’m tempted to go back to previous build and then see if reinstall does anything- or do a fresh install

anyone seen the Ultra Performance power setting yet - doesn't appear on my machine.. (??)

Kari said:

Fellow geeks on any 17xxx build using subscription based Click-to-Run installed Office 2016 (O365 Personal / Home / Business / Enterprise), I would be very pleased if you would tell about what you see when running the following command in elevated Command Prompt:

cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /dstatus

In case you are running 64 bit Office, the command is:

cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus

Screenshot shows what you should see, one licensed Office installation:

Attachment 177297
(Click to enlarge.)

I've lately had a lot of issues with Office, it remains activated only five days then deactivating itself and giving continuous account errors when connecting to services like OneDrive, above command showing two SKUs / installations, one as in above "Everything OK!" screenshot (yellow highlight) and then another unlicensed "Grace Edition" with 5 day grace period (blue highlight):

Attachment 177299
(Click to enlarge.)

I am trying to get to the bottom of this weird issue, would appreciate any feedback from you guys. I suspect underlying issue has something to do with Windows Insider Preview builds, and probably also with the way I prepare my custom W10 deployment images.

Thanks in advance,

Kari

Office runs fine here - Only the first part (yellow) when running your script.

Code:

Microsoft Windows [Version 10.0.17101.1000]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
PRODUCT ID: 00202-51030-34637-AA667
SKU ID: 149dbce7-a48e-44db-8364-a53386cd4580
LICENSE NAME: Office 16, Office16O365ProPlusR_Subscription1 edition
LICENSE DESCRIPTION: Office 16, TIMEBASED_SUB channel
BETA EXPIRATION: 01. 01. 1601
LICENSE STATUS:  ---LICENSED---
ERROR CODE: 0x4004FC04 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the application is running within the timebased validity period.
REMAINING GRACE: 58 days  (83760 minute(s) before expiring)
Last 5 characters of installed product key: BWM6P
---------------------------------------
---------------------------------------
---Exiting-----------------------------

C:\WINDOWS\system32>

RedStarFire said:

HI, I realize that the Ultimate Performance Power Mode isn't enabled for devices with batteries but, is there a way to force enable it anyways?

Only available on Windows 10 Pro for Workstations specific builds. Is that the build you have installed?

BugMeister said:

anyone seen the Ultra Performance power setting yet - doesn't appear on my machine.. (??)

Same as above, you have to have that build first before you can even see it.

BugMeister said:

anyone seen the Ultra Performance power setting yet - doesn't appear on my machine.. (??)

It's under Hide additional power plans...

Kari said:

Fellow geeks on any 17xxx build using subscription based Click-to-Run installed Office 2016 (O365 Personal / Home / Business / Enterprise), I would be very pleased if you would tell about what you see when running the following command in elevated Command Prompt:

cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /dstatus

In case you are running 64 bit Office, the command is:

cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus

Screenshot shows what you should see, one licensed Office installation:

Attachment 177297
(Click to enlarge.)

I've lately had a lot of issues with Office, it remains activated only five days then deactivating itself and giving continuous account errors when connecting to services like OneDrive, above command showing two SKUs / installations, one as in above "Everything OK!" screenshot (yellow highlight) and then another unlicensed "Grace Edition" with 5 day grace period (blue highlight):

Attachment 177299
(Click to enlarge.)

I am trying to get to the bottom of this weird issue, would appreciate any feedback from you guys. I suspect underlying issue has something to do with Windows Insider Preview builds, and probably also with the way I prepare my custom W10 deployment images.

Thanks in advance,

Kari

Only one showing.

Code:

Microsoft Windows [Version 10.0.17604.1000]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
PRODUCT ID: 00201-10965-09322-AA402
SKU ID: b58a5943-16ea-420f-a611-7b230acd762c
LICENSE NAME: Office 16, Office16O365HomePremR_Subscription4 edition
LICENSE DESCRIPTION: Office 16, TIMEBASED_SUB channel
LICENSE STATUS:  ---LICENSED---
ERROR CODE: 0x4004FC04 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the application is running within the timebased validity period.
REMAINING GRACE: 60 days  (87182 minute(s) before expiring)
Last 5 characters of installed product key: RRDWR
---------------------------------------
---------------------------------------
---Exiting-----------------------------