Tripredacus

I can only find INFO notices...

The "compatibility issues" likely have to do with permissions on any shared volumes. If you keep these truly separate, or have a shared volume that is FAT32 or a network share, you probably won't run into that problem. Using a VM depends on what kinds of programs you are going to be playing. If you are wanting to run 16bit games, a VM isn't an ideal solution at least in my experience.

Welcome to the MSFN!

I feel bad if that one guy actually put his cat down if that turns out to be true.

It seems the process is more than "just turn it on." Enabling it on my test system does not actually enable it until I have it install a Platform Key. After this is done, then the message goes away.

We are not affiliated with Microsoft, so we don't have any real input about how Windows is changed in the future. We are mostly users and enthusiasts of computing.

The main difference between a tablet/phone with an OS and a desktop/notebook computer you buy from the store or online is that the desktop computer has a noticeable cost of the operating system. Most people can tell the price of the OS, as you can buy it separately or you can get a computer without an OS on it or build it yourself. With a mobile device, there is no discernable value placed on the OS. You can't go buy the OS that is on an iPhone or a Droid. I think then people don't actually care about the OS on their phones like desktop people do. Windows RT doesn't follow the mobile OS model. The price is fairly evident of it. Since Microsoft still hasn't released RT, its unknown what the actual cost of the OS is per product, but I suspect it is somewhere around what a Windows Embedded OS costs. But another part of your quote is the life of a device. In the US this is tricky. For the most part, mobile devices are purchased through a wireless carrier. The device has a customized OS from that carrier. So something I can relate to personally, where my wireless carrier is the one who has decided the life of the phone that I have. While there is a newer OS version available, the wireless company has blocked my phone from being able to get it. If I want to get the new OS, I have to buy a new phone. There is nothing wrong with the one I have. In the past, we had the ability to "root" a phone that let you put whatever you want on there, but now that is illegal. If Microsoft succeeds at the mobile market, will they also join into this trend in order to force people to buy new devices?

Look at the oobeSystem pass in the first post of this thread: http://www.msfn.org/board/topic/139572-ask-your-seven-xml-here/

If you have Windows 8 on a GPT disk and SecureBoot isn't enabled, and then update to Windows 8.1, a message appears on the screen saying SecureBoot isn't configured properly. The solution found online of enabling SecureBoot in the BIOS (presuming you have that option) doesn't make the message go away. Has anyone actually fixed this problem?

If you have a computer with Windows 8 that was installed by an OEM on a GPT disk, the Windows 8.1 update from the Store will create a second recovery partition! Alternatively, if your OS is installed on an MBR disk, the 2nd partition is not created. This second partition is seen as a 350MB Recovery partition. For example a standard deployment of Windows 8 on GPT with recovery partition and diskpart: DISKPART> list part Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Recovery 300 MB 1024 KB Partition 2 System 100 MB 301 MB Partition 3 Reserved 128 MB 401 MB Partition 4 Primary 50 GB 529 MB Partition 5 Primary 5000 MB 50 GB The above is outlined as: Part 1 = WindowsRE (winre.wim) Part 2 = BCD/boot file location Part 3 = MSR Part 4 = OS Part 5 = Recovery Image (install.wim) After the update to Windows 8.1, it will stick a new Recovery partition after the OS. Here is the new layout including details: DISKPART> sel disk 0 Disk 0 is now the selected disk. DISKPART> list part Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Recovery 300 MB 1024 KB Partition 2 System 100 MB 301 MB Partition 3 Reserved 128 MB 401 MB Partition 4 Primary 50 GB 529 MB Partition 5 Recovery 350 MB 50 GB Partition 6 Primary 5000 MB 51 GB DISKPART> sel part 1 Partition 1 is now the selected partition. DISKPART> detail part Partition 1 Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac Hidden : Yes Required: No Attrib : 0X8000000000000000 Offset in Bytes: 1048576 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 3 Windows RE NTFS Partition 300 MB Healthy Hidden DISKPART> sel part 5 Partition 5 is now the selected partition. DISKPART> detail part Partition 5 Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac Hidden : Yes Required: Yes Attrib : 0X8000000000000001 Offset in Bytes: 54401171456 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 5 NTFS Partition 350 MB Healthy Hidden The update goes through a checklist when updating: 2013-10-25 09:41:16, Info SP F Suspend bitlocker if needed 2013-10-25 09:41:16, Info SP S Boot WinPE 2013-10-25 09:41:16, Info SP S Prepare SafeOS for rollback 2013-10-25 09:41:16, Info SP S Set SafeOS boot entry as the default boot entry 2013-10-25 09:41:16, Info SP S Cleanup safe OS mount directory 2013-10-25 09:41:16, Info SP S Apply WIM file PathForNewOS, index 4 to C:\$WINDOWS.~BT\NewOS 2013-10-25 09:41:16, Info SP S Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /postoobe for phase 3 2013-10-25 09:41:16, Info SP S Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /presysprep for phase 0 2013-10-25 09:41:16, Info SP S Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /postsysprep for phase 1 2013-10-25 09:41:16, Info SP S Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /preoobe for phase 2 2013-10-25 09:41:16, Info SP S Set entropy for C:\$WINDOWS.~BT\NewOS 2013-10-25 09:41:16, Info SP S Add boot entry for C:\$WINDOWS.~BT\NewOS\WINDOWS. Locale = en-US2013-10-25 09:41:16, Info SP S Set OS Switch rollback checkpoint 2013-10-25 09:41:16, Info SP S Backup the recovery partition to C:\$WINDOWS.~BT\Sources\RecoveryPartitionBackup 2013-10-25 09:41:16, Info SP S Apply EAs for C:\$WINDOWS.~BT\NewOS 2013-10-25 09:41:16, Info SP S Install Dynamic Updates 2013-10-25 09:41:16, Info SP S Install Driver DU Updates 2013-10-25 09:41:16, Info SP S Install OS updates (DU) to keep installation up-to-date 2013-10-25 09:41:16, Info SP S Relocate OS from C:\$WINDOWS.~BT\NewOS to C:\ 2013-10-25 09:41:16, Info SP S Add boot entry for C:\WINDOWS. Locale = en-US 2013-10-25 09:41:16, Info SP S Prepare the new OS for first boot 2013-10-25 09:41:16, Info SP S Setup the recovery partition 2013-10-25 09:41:16, Info SP S Orchestrate OS switch for NewOS with safe OS SafeOS and rollback OS ExternalRollback. DelayedSwitch: 0 2013-10-25 09:41:16, Info SP S Copy log files from C:\$WINDOWS.~BT\Sources\Panther to C:\WINDOWS Attached is selected entries from the setupact.log after the update, which shows some of the things that the update does. Things left out is when the update downloads and install.wim, mounts it with DISM, scans the existing OS for applicable drivers and packages and injects them, unmounts the image and them uses DISM to apply it to the hard drive. Regarding the extra recovery partition, there does not seem to be a way to prevent it from happening. neatstuff.txt

Will see to getting it changed.

You may be able to do it with DISM, which has its own progress bar.

First problem, you specify AutoLogon but no password. Do not use empty objects. Also, you can only use that answer file on an Enterprise or Server OS and you need to specify a password for the Administrator account. Second, your answer file doesn't have any objects that hide OOBE pages.

Microsoft uses Torrents nowadays?

Sounds good, but take it easy on the tags next time.

Regarding that SecureBoot message. Its confusing a lot of people because normally you do not see the build number on the desktop unless Windows isn't activated. However this is not the case. You can be activated and still see that message. Also, it is not a requirement to enable SecureBoot on UEFI systems unless they are a tablet. So if any Windows 8 system was installed on a GPT disk but SecureBoot is not enabled, the user will see that message after updating to Windows 8.1 from the Store. (it is possible a clean install also does this but I haven't tested it yet). And to make matters worse, not all hardware that does support UEFI for GPT boot (especially 3rd party emulators like MSI's 2.2TB Infinity) even have a SecureBoot option in the BIOS. I'm not sure why Microsoft would make all Windows 8.1 OSes show this message, except maybe to brag that the hardware it is installed on isn't certified for the OS. Also found this online, maybe Charlotte can use it...

Jagex is based in the UK.

--JorgeA I had no idea it even came out? Didn't some Apple stuff come out this week? My twitter was full of reaction to those, not a peep about a Surface.

Forum rule 2e applies to your question.

Welcome to the MSFN!

I'd be down for a Win8 mod that showed this.

Ok I have one answer so far. If you have purchase your computer and Windows 8 came pre-installed, or Windows 7 was pre-installed as part of the Downgrade Rights program, but are using a local account only, you can ask the computer manufacturer for a Windows 8.1 Recovery DVD. As I would expect anytime you go to an OEM to ask for recovery media, they usually charge for it. I am still waiting to see what the case would be if the computer was purchased with the OEM System Builder Kit version of Windows 8 installed.

I am seeing if there are any alternate ways. I wouldn't be surprised if MS hadn't considered that option before preparing the product for release.

A split topic greeting, not sure I've seen that before.

What did you do, Ray?