Win8.1 on reboot like it's newly installed + empty metro

[kamelot]

Hello,
I have an issue with Win8.1 Pro x64. I have upgraded from 8. About every 5-6 days after I turn on my laptop, Win8 behaves like it was just newly installed. By that I mean that after I login into the system I get a screen with "We're setting things up for you" and messages about installing apps from the store. After that finishes, an empty metro screen is displayed. Then, after I choose to reboot, system starts OK.

This does not happen every reboot, approximately on every fifth/sixth.
Is there a way how to fix this? I find it extremely annoying when I have to wait about 5 minutes just to do another reboot. And what if one day it does not reboot correctly from the empty screen?

Thanks in advance!

 

[Saltgrass]

What you are seeing appears to be exactly what you might see if you had set your system to use a CustomRefresh.wim image to reset your system. Since it does not contain some files as noted below, it appears your system is missing those files during boot or possibly even booting to another image or repair version of an image. But just speculating right now.

Are you getting any messages that would make you think Windows is going into some type of Repair situation?

If it continues, you might check the list below and see if you can think of any reason those files might not be loaded during the problem boot instances.

Recovery images do not contain your documents, personal settings, user profiles, or apps from Windows Store,
because that information is preserved at the time you refresh your PC.

If you want, you might run the command below in an administrative command prompt. You could zip the resulting text file and attach, or just list it if you want. Maybe someone will see something relevant to this problem.

bcdedit /enum all > %userprofile%\Desktop\BCDtext.txt

 

[XweAponX]

It's loading a TEMPORARY PROFILE on you at random intervals.

Do what Saltgrass Suggests, and use "Code" (#) to wrap code tags around it, then we can slide up and down looking through it.

If the Temp Profile takes over, you will have to rebuild your User Account, it's not that hard but you can only do it from within Admin Safe Mode.

 

[kamelot]

Thanks, I haven't set any CustomRefresh.wim.
Also, when I got empty screen, only thing I have there is my account photo in upper right corner - can be this still temp account?

Output of bcdedit I ran on my PC is here:

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  sk-SK
inherit                 {globalsettings}
integrityservices       Enable
default                 {current}
resumeobject            {be6c3aac-375a-11e3-923e-8c86d35a0c5e}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30


Windows Boot Loader
-------------------
identifier              {5aea2518-375b-11e3-923e-8c86d35a0c5e}
device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{5aea2519-375b-11e3-923e-8c86d35a0c5e}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
locale                  sk-SK
inherit                 {bootloadersettings}
displaymessage          Recovery
displaymessageoverride  Recovery
osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{5aea2519-375b-11e3-923e-8c86d35a0c5e}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes


Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 8.1
locale                  sk-SK
inherit                 {bootloadersettings}
recoverysequence        {5aea2518-375b-11e3-923e-8c86d35a0c5e}
integrityservices       Enable
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {be6c3aac-375a-11e3-923e-8c86d35a0c5e}
nx                      OptIn
bootmenupolicy          Standard


Windows Boot Loader
-------------------
identifier              {ea4e3749-9460-11e0-a8ab-c59eff6bbdbf}
device                  ramdisk=[C:]\Recovery\ea4e3749-9460-11e0-a8ab-c59eff6bbdbf\Winre.wim,{ea4e374a-9460-11e0-a8ab-c59eff6bbdbf}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\ea4e3749-9460-11e0-a8ab-c59eff6bbdbf\Winre.wim,{ea4e374a-9460-11e0-a8ab-c59eff6bbdbf}
systemroot              \windows
nx                      OptIn
winpe                   Yes


Windows Boot Loader
-------------------
identifier              {ea4e374d-9460-11e0-a8ab-c59eff6bbdbf}
device                  ramdisk=[C:]\Recovery\ea4e374d-9460-11e0-a8ab-c59eff6bbdbf\Winre.wim,{ea4e374e-9460-11e0-a8ab-c59eff6bbdbf}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
locale                  sk-SK
inherit                 {bootloadersettings}
displaymessage          Recovery
displaymessageoverride  Recovery
osdevice                ramdisk=[C:]\Recovery\ea4e374d-9460-11e0-a8ab-c59eff6bbdbf\Winre.wim,{ea4e374e-9460-11e0-a8ab-c59eff6bbdbf}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes


Resume from Hibernate
---------------------
identifier              {be6c3aac-375a-11e3-923e-8c86d35a0c5e}
device                  partition=C:
path                    \WINDOWS\system32\winresume.exe
description             Windows Resume Application
locale                  sk-SK
inherit                 {resumeloadersettings}
recoverysequence        {5aea2518-375b-11e3-923e-8c86d35a0c5e}
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No


Resume from Hibernate
---------------------
identifier              {ea4e374b-9460-11e0-a8ab-c59eff6bbdbf}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  sk-SK
inherit                 {resumeloadersettings}
recoverysequence        {ea4e374d-9460-11e0-a8ab-c59eff6bbdbf}
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No


Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume1
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  sk-SK
inherit                 {globalsettings}
badmemoryaccess         Yes


EMS Settings
------------
identifier              {emssettings}
bootems                 No


Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200


RAM Defects
-----------
identifier              {badmemory}


Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}


Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}


Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200


Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}


Device options
--------------
identifier              {5aea2519-375b-11e3-923e-8c86d35a0c5e}
description             Windows Recovery
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi


Device options
--------------
identifier              {ea4e374a-9460-11e0-a8ab-c59eff6bbdbf}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\ea4e3749-9460-11e0-a8ab-c59eff6bbdbf\boot.sdi


Device options
--------------
identifier              {ea4e374e-9460-11e0-a8ab-c59eff6bbdbf}
description             Windows Recovery
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\ea4e374d-9460-11e0-a8ab-c59eff6bbdbf\boot.sdi


Device options
--------------
identifier              {ea4e374f-9460-11e0-a8ab-c59eff6bbdbf}
description             Windows Setup
ramdisksdidevice        partition=C:
ramdisksdipath          \$WINDOWS.~BT\Sources\SafeOS\boot.sdi

 

[XweAponX]

It will usually notify you that a TEMP Profile is loaded - But you can check this by going into your USERS folder and looking for a user named "Temp" - If there is one, then you need to re-create your local user profile. So if you are using an MS account to log in, change it to a LOCAL account, then create a new Local account, and you can move all of your corrupted user folders into the new account folder.

Since Temp Profile is a vista problem that exists in Windows 7 and 8, the tutorial is in the Vista boards. and I'll have to look up the link

 

[kamelot]

I don't have Temp folder ic C:\Users. I'm using MS account to log in to Windows 8, not a local account.

 

[Saltgrass]

I don't see anything that sticks out in your BCD store listing, except for one part which I have to check on my Legacy Install. You are not showing a path entry in the Boot Manager, but it may not be required. You do have many unused entries, but those should be OK.

Your situation, to me, seems to be a little different in that you can log in. I was under the impression that if your User Profile was not loading at all, you would not be able log on, but I could be mistaken.

I do agree, that since you are using the Online account, there might be some sort of network situation. Perhaps switching to a local account for a while might help clear things up. I think I would hold off on changing your user folders around, at least until the local account showed the same symptoms.