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

AndreTen · 16 Feb 2018

johngalt said:

I have had Fast Start cause so many issues on my Desktop that it is one of the first things I turn off after a new build.

It stays disabled for me. Must be for couple of months now...

JGToy · 16 Feb 2018

For this one (17101) all my machine updated without any hiccups even a 2005/2006 Dell Dimension 9100.
Of course I haven't tested everything as you guys but, for what I need and little bit extras all is running smooths.

martyfelker · 16 Feb 2018

I have always disabled fast start. Multiboot system

magilla · 16 Feb 2018

Wynona said:

Yes, it did. That's why I was so excited.

Glad for you, sad for me. I followed Shawn’s steps, restarted, no change. Still goes ‘dead’ when in sleep mode and I have to use macrium win pe boot to get it started again.

Wynona · 16 Feb 2018

magilla said:

Glad for you, sad for me. I followed Shawn’s steps, restarted, no change. Still goes ‘dead’ when in sleep mode and I have to use macrium win pe boot to get it started again.

You seem to have two different problems, Magilla. I don't have a problem with sleep at all.

BTW, did you do powercfg -h off in an admin command prompt? That's supposed to turn off hibernation. And it's probably in the tutorial you followed, but just in case.

Wynona · 16 Feb 2018

johngalt said:

What did you copy and paste as a command?

Never mind, John.

I inadvertently installed Office 365 2016 32 bit instead of 64 bit. That's why it wouldn't work.

flybynite · 16 Feb 2018

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

Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing-----------------------
-----------------------------------------
PRODUCT ID: 00398-30000-00000-AA759
SKU ID: c3b2612d-58ee-4d9b-ad9d-7568decb29f7
LICENSE NAME: Office 19, Office19ProPlus2019R_PrepidBypass edition
LICENSE DESCRIPTION: Office 19, RETAIL(Free) channel
BETA EXPIRATION: Monday 12 31 2018 6:59:59
LICENSE STATUS: ---LICENSED---
ERROR CODE: 0x4004FC05 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the application has a perpetual grace period.
Last 5 characters of installed product key: BWTH9
--------------------------------------
--------------------------------------
----Exiting-------------------------

bordi · 17 Feb 2018

bordi said:

Seems unlike me 17604 is a heavy sleeper, it wouldn’t wake up just by a shake of the mouse.
I had to do it from the on and off switch

magilla said:

But, did the turning off of fast start solve your problem @Wynona? That's what I'd like to know.

Wynona said:

Yes, it did. That's why I was so excited.

Didn’t work for me either, we’ve had this issue before as I remember
Pain in the neck having to type the password so many times throughout the day:)

johngalt · 17 Feb 2018

Wynona said:

Never mind, John.

I inadvertently installed Office 365 2016 32 bit instead of 64 bit. That's why it wouldn't work.

Yep - that's why I asked :)

flybynite said:

Microsoft (R) Windows Script Host Version 5.812Copyright (C) Microsoft Corporation. All rights reserved.---Processing-----------------------------------------------------------------PRODUCT ID: 00398-30000-00000-AA759SKU ID: c3b2612d-58ee-4d9b-ad9d-7568decb29f7LICENSE NAME: Office 19, Office19ProPlus2019R_PrepidBypass editionLICENSE DESCRIPTION: Office 19, RETAIL(Free) channelBETA EXPIRATION: Monday 12 31 2018 6:59:59LICENSE STATUS: ---LICENSED---ERROR CODE: 0x4004FC05 (for information purposes only as the status is licensed)ERROR DESCRIPTION: The Software Licensing Service reported that the application has a perpetual grace period.Last 5 characters of installed product key: BWTH9---------------------------------------------------------------------------------Exiting-----------------------------

If you post the above in a code tag then it becomes much easier to read.

Like so:

Code:

Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing-----------------------------------------------------------------
PRODUCT ID: 00398-30000-00000-AA759SKU ID: c3b2612d-58ee-4d9b-ad9d-7568decb29f7
LICENSE NAME: Office 19, Office19ProPlus2019R_PrepidBypass edition
LICENSE DESCRIPTION: Office 19, RETAIL(Free) channel
BETA EXPIRATION: Monday 12 31 2018 6:59:59
LICENSE STATUS:  ---LICENSED---
ERROR CODE: 0x4004FC05 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the application has a perpetual grace period.
Last 5 characters of installed product key: BWTH9
---------------------------------------------------------------------------------Exiting-----------------------------

johngalt · 17 Feb 2018

bordi said:

Didn’t work for me either, we’ve had this issue before as I remember
Pain in the neck having to type the password so many times throughout the day:)

That's why I use a PIN lol. Seriously.

My Microsoft account PW is 24 chars including letters, numbers, and special characters from sets 1-3, with no look alike characters. Typing that thing in repeatedly is not gonna happen. I barely remember it as it is...