If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#31
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
"R. C. White" wrote:
For several years now, my WU setting hasn't changed. It is still, "Download updates but let me choose whether to install them." This has always worked very well for me. And I very seldom choose to NOT install any of them. I can't make head nor tails of the "explanation" that is always offered, anyhow. (Sounds like boilerplate that seldom says anything informative - or specific to the current update.) If I install one and it doesn't work, I can blame Microsoft; if I don't install a recommended update and my computer dies, "I've got only me to blame 'cause Mama tried", as Merle Haggard sang. To some degree the use of generic boilerplace without lots of details is necessary; the more information provided about the vulnerability the easier it is for the nasty guys to figure out how to exploit it on machines that haven't been patched...and even with the imprecise descriptions of the vulnerabilities we've often seen attacks begin very soon after the bulletins are released. If you're looking for more information about what a patch addresses, you might get a little more than what's in the SB by clicking through the CVE (Common Vulnerabilities and Exposures) link in the Microsoft Securit Bulletin, then stepping through the "references" list on the CVE page. As an example, MS14-066 (the out-of-season server patch released recently) addresses CVE-2014-6321, and its page in CVE links in turn to related pages from Microsoft, BeyondTrust.com, US-CERT.GOV, and cert.org; the CVE page header also contains a link to nist.gov. Joe |
Ads |
#33
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
""...winston‫"" wrote in message ... SC Tom wrote: "SC Tom" wrote in message ... ""...winston‫"" wrote in message ... November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: https://support2.microsoft.com/kb/3000850 See the article for new features and improvements. Do you have to be logged in with a Microsoft account in order to install this? Seems to me that I was logged in with my local account when I upgraded to 8.1, so I don't know if that makes any difference or not. That's the only reason I can think of for the continual failure of this rollup. Nope, never mind, that's not it. Hi, SCTom Is your Antivirus program AVAST. There are some reported issues that the update fails when AVAST is installed. See https://forum.avast.com/index.php?topic=160717.0 http://answers.microsoft.com/en-us/w...5-3ae1a72b0b1a Well, I got it to install today. After trying it for the umpteenth time early this morning, and having if fail for the umpteenth time, I came across this article on line: http://www.msfn.org/board/topic/173051-kb3000850-big-update-windows-812/page-2 About a third of the way down is a post about making sure these two folders exist: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessibility C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools I didn't have either folder, so I created them (well, tried to anyhow). The first one was no problem, but the second was a no go. That may be a protected name or it may be that \Windows Accessories exists and the system points to that as the \Accessories folder. There is already a \System Tools folder under that, so I let that one go and tried to install the update again. One of two things happened; either there was a change to the rollup by Microsoft since my early morning attempt, or the \Accessibility folder was a necessity. Either way, KB3000850 finally installed. It doesn't appear to have changed anything, and I may not have really needed it, but it just pushes my buttons when something that should be so easy isn't. I'm sure a number of people here know exactly what I mean :-) -- SC Tom |
#34
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
On 11/22/2014 7:12 AM, Crkeehn wrote:
On 11/21/2014 8:41 PM, Char Jackson wrote: On Wed, 19 Nov 2014 01:46:19 -0700, "...winston?" wrote: November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: https://support2.microsoft.com/kb/3000850 See the article for new features and improvements. The discussion makes it look like this is something that people are proactively downloading and installing. Will this not also be available via Windows Update at some point? Or if not the rollup in its entirety, perhaps the functional equivalent in multiple smaller pieces? It's classed as an optional update. It may not show up for a while. Carl It showed up yesterday 11/23/14 on this desktop. The server seemed to have problems of some type, resulting in longer than normal download times. Intermittently looking at the install process with task manager, since it was taking an unusual amount of time, showed significant activity in various "services" as the install process ran. Antivirus, update helper, and so forth. |
#35
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
charlie wrote: On 11/22/2014 7:12 AM, Crkeehn wrote: On 11/21/2014 8:41 PM, Char Jackson wrote: On Wed, 19 Nov 2014 01:46:19 -0700, "...winston?" wrote: November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: https://support2.microsoft.com/kb/3000850 See the article for new features and improvements. The discussion makes it look like this is something that people are proactively downloading and installing. Will this not also be available via Windows Update at some point? Or if not the rollup in its entirety, perhaps the functional equivalent in multiple smaller pieces? It's classed as an optional update. It may not show up for a while. Carl It showed up yesterday 11/23/14 on this desktop. The server seemed to have problems of some type, resulting in longer than normal download times. Intermittently looking at the install process with task manager, since it was taking an unusual amount of time, showed significant activity in various "services" as the install process ran. Antivirus, update helper, and so forth. I downloaded the iso file of windows 8.1 from microsoft and it has the latest November update. I did a clean reinstall of win 8.1. ............................................. Create installation media for Windows 8.1 http://windows.microsoft.com/en-us/w...-refresh-media ............................................ HS |
#36
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
"HS" escreveu na mensagem ...
I downloaded the iso file of windows 8.1 from microsoft and it has the latest November update. I did a clean reinstall of win 8.1. ............................................ Create installation media for Windows 8.1 http://windows.microsoft.com/en-us/w...-refresh-media ........................................... Some people bought OEM Windows 8 preinstalled on machine. In this case and using the above link, how do you do a reinstall without serial key? |
#37
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
BenSmith wrote: "HS" escreveu na mensagem ... I downloaded the iso file of windows 8.1 from microsoft and it has the latest November update. I did a clean reinstall of win 8.1. ............................................ Create installation media for Windows 8.1 http://windows.microsoft.com/en-us/w...-refresh-media ........................................... Some people bought OEM Windows 8 preinstalled on machine. In this case and using the above link, how do you do a reinstall without serial key? I would first "recover" the product key with a program like Magic Jelly Bean and store it is a very safe place before doing a fresh installation https://www.magicaljellybean.com/ I have also used ProduKey http://www.nirsoft.net/utils/product_cd_key_viewer.html Try both for a peace of mind HS |
#38
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
HS wrote:
BenSmith wrote: "HS" escreveu na mensagem ... I downloaded the iso file of windows 8.1 from microsoft and it has the latest November update. I did a clean reinstall of win 8.1. ............................................ Create installation media for Windows 8.1 http://windows.microsoft.com/en-us/w...-refresh-media ........................................... Some people bought OEM Windows 8 preinstalled on machine. In this case and using the above link, how do you do a reinstall without serial key? I would first "recover" the product key with a program like Magic Jelly Bean and store it is a very safe place before doing a fresh installation https://www.magicaljellybean.com/ I have also used ProduKey http://www.nirsoft.net/utils/product_cd_key_viewer.html Try both for a peace of mind HS If the discussion is about Windows 8 OEM, you need a different recipe than MagicJellyBean... Something I picked up in some thread here, only a couple days ago. the new detail, was with respect to where the key is stored. Now, maybe the key is obtainable both ways, but at least this gives a way to get it, without a working Windows running on the computer. ******* 1- Download and create a Linux Live CD, Linux Mint or Ubuntu for example 2 - launch it 3- open the console called Terminal 4- type: ls /sys/firmware/acpi/tables , it will shows you if you have a MSDM table 5- then type: sudo hd /sys/firmware/acpi/tables/MSDM the license will shows up on the right of the output. Then now you can use it to install Win8.xx ******* Now, while that is interesting, another data point is, that a Windows 8 Retail install (of matching install type), will automatically activate when presented with the BIOS key. So while you can extract the key from MSDM, it may not even be necessary to have the key in hand. You would likely need to match Core with Core, or Pro with Pro, so if your OEM machine came with Core (a.k.a Home), then you'd likely want to be attempting to install a retail one similar to that, so it will activate without complaint. Maybe a universal DVD (with ei.cfg removed) could be used for the installation. An MSDN subscription image (via Torrent), could give you materials for several different flavors of after-market install. For other OEM OSes (Windows 7 or earlier), they are BIOS SLIC activated. But there isn't a unique key in there. The key that goes with SLIC is a "bulk" key of some sort. The key printed on the COA is a different key, and is a unique value per machine (Windows 7 machines have a COA, Windows 8 machines do not). And even with MagicJellyBean, you have to remember what you're extracting. The "bulk" key would not be of any use to you, whereas someone who reinstalled the OS and inserted the COA key, that key would be reusable if extracted with the Magic. So if the user did an install based on COA, did phone activation when prompted, later the COA sticker got scratched up, the MagicJellyBean can help in that case. I don't have a Win8 OEM machine here, so I don't have the materials to verify the new MSDM info. I'm surprised the key isn't encrypted. HTH, Paul |
#39
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
"HS" escreveu na mensagem ... I downloaded the iso file of windows 8.1 from microsoft and it has the latest November update. I did a clean reinstall of win 8.1. ............................................ Create installation media for Windows 8.1 http://windows.microsoft.com/en-us/w...-refresh-media ........................................... "BenSmith" escreveu na mensagem ... Some people bought OEM Windows 8 preinstalled on machine. In this case and using the above link, how do you do a reinstall without serial key? "With Windows 8, Microsoft has changed from stickers that have the product key that the user has to type in when installing the operating system to new BIOS embedded product keys. The idea is that by eliminating the sticker, you eliminate one of the easier ways for nefarious users to get a legitimate product key. Eliminating the product key sticker also removes any worry that the sticker might get damaged while at the same time eliminating the long and irritating process of typing in various letters and numbers when installing the operating system. If the user has to reinstall the operating system on a machine that came with Windows 8, the installation process automatically grabs the software product key from the motherboard BIOS with no input from the user. This means that those familiar Windows product key stickers will no longer appear on the Windows 8 computers." See the entire conversation on the Microsoft Community website. |
#40
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
Paul wrote:
HS wrote: BenSmith wrote: "HS" escreveu na mensagem ... I downloaded the iso file of windows 8.1 from microsoft and it has the latest November update. I did a clean reinstall of win 8.1. ............................................ Create installation media for Windows 8.1 http://windows.microsoft.com/en-us/w...-refresh-media ........................................... Some people bought OEM Windows 8 preinstalled on machine. In this case and using the above link, how do you do a reinstall without serial key? I would first "recover" the product key with a program like Magic Jelly Bean and store it is a very safe place before doing a fresh installation https://www.magicaljellybean.com/ I have also used ProduKey http://www.nirsoft.net/utils/product_cd_key_viewer.html Try both for a peace of mind HS If the discussion is about Windows 8 OEM, you need a different recipe than MagicJellyBean... Something I picked up in some thread here, only a couple days ago. the new detail, was with respect to where the key is stored. Now, maybe the key is obtainable both ways, but at least this gives a way to get it, without a working Windows running on the computer. ******* 1- Download and create a Linux Live CD, Linux Mint or Ubuntu for example 2 - launch it 3- open the console called Terminal 4- type: ls /sys/firmware/acpi/tables , it will shows you if you have a MSDM table 5- then type: sudo hd /sys/firmware/acpi/tables/MSDM the license will shows up on the right of the output. Then now you can use it to install Win8.xx ******* Now, while that is interesting, another data point is, that a Windows 8 Retail install (of matching install type), will automatically activate when presented with the BIOS key. So while you can extract the key from MSDM, it may not even be necessary to have the key in hand. You would likely need to match Core with Core, or Pro with Pro, so if your OEM machine came with Core (a.k.a Home), then you'd likely want to be attempting to install a retail one similar to that, so it will activate without complaint. Maybe a universal DVD (with ei.cfg removed) could be used for the installation. An MSDN subscription image (via Torrent), could give you materials for several different flavors of after-market install. For other OEM OSes (Windows 7 or earlier), they are BIOS SLIC activated. But there isn't a unique key in there. The key that goes with SLIC is a "bulk" key of some sort. The key printed on the COA is a different key, and is a unique value per machine (Windows 7 machines have a COA, Windows 8 machines do not). And even with MagicJellyBean, you have to remember what you're extracting. The "bulk" key would not be of any use to you, whereas someone who reinstalled the OS and inserted the COA key, that key would be reusable if extracted with the Magic. So if the user did an install based on COA, did phone activation when prompted, later the COA sticker got scratched up, the MagicJellyBean can help in that case. I don't have a Win8 OEM machine here, so I don't have the materials to verify the new MSDM info. I'm surprised the key isn't encrypted. HTH, Paul Maybe someone with an OEM unit will attempt the Linux based MSDM route. - and actually verify it shows all Product Key digits and not just the last 5. Office 2013 retail comes with a product key (no media, download only, Click to Run Install). The included Product Key in the retail package is a key with the right to download and install (creation of a MSFT account is necessary too). If one wishes to find 'their' installed product key, it is not the one in the package, but the one available in their Microsoft account. -- ....winston msft mvp consumer apps |
#41
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
Homero wrote: "With Windows 8, Microsoft has changed from stickers that have the product key that the user has to type in when installing the operating system to new BIOS embedded product keys. The idea is that by eliminating the sticker, you eliminate one of the easier ways for nefarious users to get a legitimate product key. Eliminating the product key sticker also removes any worry that the sticker might get damaged while at the same time eliminating the long and irritating process of typing in various letters and numbers when installing the operating system. If the user has to reinstall the operating system on a machine that came with Windows 8, the installation process automatically grabs the software product key from the motherboard BIOS with no input from the user. This means that those familiar Windows product key stickers will no longer appear on the Windows 8 computers." See the entire conversation on the Microsoft Community website. I have bought 2 laptops for my teenage granchildren in the last year. In both cases I replaced the hard disk with ssd and did a clean installation With Lenovo Twist the installation process grabbed the key from the bios With Asus Vivo book 13.3 inch) it did not do so. I had to enter the keys which I had extracted with Jelly Bean before replacing the hard disk with ssd. HS |
#42
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
On Mon, 24 Nov 2014 23:09:37 -0700, "...winston?"
wrote: I would first "recover" the product key with a program like Magic Jelly Bean and store it is a very safe place before doing a fresh installation https://www.magicaljellybean.com/ I have also used ProduKey http://www.nirsoft.net/utils/product_cd_key_viewer.html Try both for a peace of mind Keyfinder is another one. I'd offer the same advice to anyone considering replacing *any* Windows installation, particularly of unknown provenance. The installed key *should* match the one on the sticker, but even if the sticker is actually readable, you can't guarantee the printed code is the one relating to what's installed. Rod. |
#43
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
On 11/25/2014 01:09 AM, "...winston‫" wrote:
Paul wrote: HS wrote: BenSmith wrote: "HS" escreveu na mensagem ... I downloaded the iso file of windows 8.1 from microsoft and it has the latest November update. I did a clean reinstall of win 8.1. ............................................ Create installation media for Windows 8.1 http://windows.microsoft.com/en-us/w...-refresh-media ........................................... Some people bought OEM Windows 8 preinstalled on machine. In this case and using the above link, how do you do a reinstall without serial key? I would first "recover" the product key with a program like Magic Jelly Bean and store it is a very safe place before doing a fresh installation https://www.magicaljellybean.com/ I have also used ProduKey http://www.nirsoft.net/utils/product_cd_key_viewer.html Try both for a peace of mind HS If the discussion is about Windows 8 OEM, you need a different recipe than MagicJellyBean... Something I picked up in some thread here, only a couple days ago. the new detail, was with respect to where the key is stored. Now, maybe the key is obtainable both ways, but at least this gives a way to get it, without a working Windows running on the computer. ******* 1- Download and create a Linux Live CD, Linux Mint or Ubuntu for example 2 - launch it 3- open the console called Terminal 4- type: ls /sys/firmware/acpi/tables , it will shows you if you have a MSDM table 5- then type: sudo hd /sys/firmware/acpi/tables/MSDM the license will shows up on the right of the output. Then now you can use it to install Win8.xx ******* Now, while that is interesting, another data point is, that a Windows 8 Retail install (of matching install type), will automatically activate when presented with the BIOS key. So while you can extract the key from MSDM, it may not even be necessary to have the key in hand. You would likely need to match Core with Core, or Pro with Pro, so if your OEM machine came with Core (a.k.a Home), then you'd likely want to be attempting to install a retail one similar to that, so it will activate without complaint. Maybe a universal DVD (with ei.cfg removed) could be used for the installation. An MSDN subscription image (via Torrent), could give you materials for several different flavors of after-market install. For other OEM OSes (Windows 7 or earlier), they are BIOS SLIC activated. But there isn't a unique key in there. The key that goes with SLIC is a "bulk" key of some sort. The key printed on the COA is a different key, and is a unique value per machine (Windows 7 machines have a COA, Windows 8 machines do not). And even with MagicJellyBean, you have to remember what you're extracting. The "bulk" key would not be of any use to you, whereas someone who reinstalled the OS and inserted the COA key, that key would be reusable if extracted with the Magic. So if the user did an install based on COA, did phone activation when prompted, later the COA sticker got scratched up, the MagicJellyBean can help in that case. I don't have a Win8 OEM machine here, so I don't have the materials to verify the new MSDM info. I'm surprised the key isn't encrypted. HTH, Paul Maybe someone with an OEM unit will attempt the Linux based MSDM route. - and actually verify it shows all Product Key digits and not just the last 5. Office 2013 retail comes with a product key (no media, download only, Click to Run Install). The included Product Key in the retail package is a key with the right to download and install (creation of a MSFT account is necessary too). If one wishes to find 'their' installed product key, it is not the one in the package, but the one available in their Microsoft account. Belarc does more then just show you your product key. OEM or retail. -- Caver1 |
#44
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
On 25/11/2014 9:56 AM, Caver1 wrote:
On 11/25/2014 01:09 AM, "...winston‫" wrote: Paul wrote: HS wrote: BenSmith wrote: "HS" escreveu na mensagem ... I downloaded the iso file of windows 8.1 from microsoft and it has the latest November update. I did a clean reinstall of win 8.1. ............................................ Create installation media for Windows 8.1 http://windows.microsoft.com/en-us/w...-refresh-media ........................................... Some people bought OEM Windows 8 preinstalled on machine. In this case and using the above link, how do you do a reinstall without serial key? I would first "recover" the product key with a program like Magic Jelly Bean and store it is a very safe place before doing a fresh installation https://www.magicaljellybean.com/ I have also used ProduKey http://www.nirsoft.net/utils/product_cd_key_viewer.html Try both for a peace of mind HS If the discussion is about Windows 8 OEM, you need a different recipe than MagicJellyBean... Something I picked up in some thread here, only a couple days ago. the new detail, was with respect to where the key is stored. Now, maybe the key is obtainable both ways, but at least this gives a way to get it, without a working Windows running on the computer. ******* 1- Download and create a Linux Live CD, Linux Mint or Ubuntu for example 2 - launch it 3- open the console called Terminal 4- type: ls /sys/firmware/acpi/tables , it will shows you if you have a MSDM table 5- then type: sudo hd /sys/firmware/acpi/tables/MSDM the license will shows up on the right of the output. Then now you can use it to install Win8.xx ******* Now, while that is interesting, another data point is, that a Windows 8 Retail install (of matching install type), will automatically activate when presented with the BIOS key. So while you can extract the key from MSDM, it may not even be necessary to have the key in hand. You would likely need to match Core with Core, or Pro with Pro, so if your OEM machine came with Core (a.k.a Home), then you'd likely want to be attempting to install a retail one similar to that, so it will activate without complaint. Maybe a universal DVD (with ei.cfg removed) could be used for the installation. An MSDN subscription image (via Torrent), could give you materials for several different flavors of after-market install. For other OEM OSes (Windows 7 or earlier), they are BIOS SLIC activated. But there isn't a unique key in there. The key that goes with SLIC is a "bulk" key of some sort. The key printed on the COA is a different key, and is a unique value per machine (Windows 7 machines have a COA, Windows 8 machines do not). And even with MagicJellyBean, you have to remember what you're extracting. The "bulk" key would not be of any use to you, whereas someone who reinstalled the OS and inserted the COA key, that key would be reusable if extracted with the Magic. So if the user did an install based on COA, did phone activation when prompted, later the COA sticker got scratched up, the MagicJellyBean can help in that case. I don't have a Win8 OEM machine here, so I don't have the materials to verify the new MSDM info. I'm surprised the key isn't encrypted. HTH, Paul Maybe someone with an OEM unit will attempt the Linux based MSDM route. - and actually verify it shows all Product Key digits and not just the last 5. Office 2013 retail comes with a product key (no media, download only, Click to Run Install). The included Product Key in the retail package is a key with the right to download and install (creation of a MSFT account is necessary too). If one wishes to find 'their' installed product key, it is not the one in the package, but the one available in their Microsoft account. Belarc does more then just show you your product key. OEM or retail. Belarc is a God-send. It allowed me to retrieve my Windows 8 key when I was sure I had lost it. -- Sir Slimer OpenMedia Supporter www.silverlips.ca |
#45
|
|||
|
|||
November 2014 Windows 8.1 Update Rollup
On 2014-11-25, ...winston??? wrote:
..............lots skipped........... Maybe someone with an OEM unit will attempt the Linux based MSDM route. - and actually verify it shows all Product Key digits and not just the last 5. Office 2013 retail comes with a product key (no media, download only, Click to Run Install). The included Product Key in the retail package is a key with the right to download and install (creation of a MSFT account is necessary too). If one wishes to find 'their' installed product key, it is not the one in the package, but the one available in their Microsoft account. Does this mean that the OEM computers will NEVER get a bios updated? I think that I made the right decision to update my computer several months ago rather than getting an "off the shelf" product...... |
Thread Tools | |
Display Modes | Rate This Thread |
|
|