Tripredacus

I'm going based on what MagicAndre has posted about Windows 8 in the past. I trust his judgement as his knowledge of the inner workings of Windows is way better than mine. But in reality Windows 8.1 isn't any big change from Windows 8 from what I can tell but if you exclude the Start Screen and removal of the Start Menu, Windows 8 is a fine upgrade from Windows 7. Of course those two things I mentioned are also detractors for me which is why I am still on Windows 7.

I haven't heard anything. It seems to be that MS is going away from traditional OS releases and going into making update versions. After all, we got Win8.1 less than a year after Win8 came out.

The first page is Articulate Presenter's browser detection script. My browser doesn't let me view "the site" either because I have scripting disabled. What browser are you using?

Who implied that? 8.1 isn't really an improvement over 7 in the very same ways 8.0 isn't an improvement. It's an App Delivery System designed by Microsoft to do one thing: You're only looking at the part of the OS, specifically the Start Screen. If you ignore that, then it is an improvement.

Take a look at either of ChrisR's or Kel's project threads in this section.

I wouldn't worry about the monitors in Device Manager. If you wanted to clear yourself of anomalies there, reboot into Safe Mode and delete all the items under where the monitors show up. The reason for Safe Mode is that there may be more devices that appear there. Which motherboard do you have and what display do you have?

This behaviour isn't browser specific. Do you have AdBlock Plus installed?

That's usually the fault of the video driver. I have seen in several cases where the same hardware will or won't run WinSAT at first boot depending what video driver is installed.

Yes this is the case, however I have the same pasting problem with Firefox as well.

In my experience, there is always warnings in the CBS logs, even on a clean source with nothing added. Usually you only go into the cbs.log when troubleshooting a problem. What problem are you experiencing?

I vote for a "you first" approach... http://www.modern.ie/en-us/11percent Sorry! We found the following errors (301) http://jigsaw.w3.org/css-validator/validator?profile=css21&warning=0&uri=http%3A%2F%2Fwww.modern.ie%2Fen-us%2F11percent 20 Errors, 2 warning(s) http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.modern.ie%2Fen-us%2F11percent

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?