erpdude8
Content Type
Profiles
Forums
Events
Posts posted by erpdude8
-
-
On 1/27/2020 at 7:16 PM, VistaLover said:
Isn't it ironic/cheeky they still mention Vista SP1+ as a supported OS, though? ...
while the MSE app itself works on Vista SP1/SP2, the MSE definition/signature files from mid-2017 & beyond do not support Vista (unless you can find a site that has a copy of the old MSE definition updates from early 2017 that worked for MSE on Vista)
0 -
On 1/21/2020 at 5:32 AM, roytam1 said:
download (for fun!): http://o.rths.ml/gpc/files1.rt/phoenix-0.5-cl933-tls12.7z
the o.rths.ml site is currently not working, roytam1 [all browsers from many different PCs I'm using can't connect to that site but other sites work fine]
why?0 -
-
I've just manually installed the 1/14/2020 MSE definition files onto MSE for Win7 and the MSE v4.10.209 app still runs as normal - no EOL nags appear in the MSE app.
0 -
MSE still working with no EOL nags
just applied the 1/14/2020 MSE definition updates more than an hour ago on a Win7 laptop - MSE runs fine as usual
also installed the newly released Jan. 2020 KB4534310 rollup on Win7 as well0 -
38 minutes ago, Jody Thornton said:
Now does this mean that the new MS Edge will only support Windows 7 for the same period of time?
Neowin has answered that question for you yesterday, Jody
so the answer is yes0 -
On 11/21/2019 at 11:16 PM, Jaguarek62 said:
Yeah, so it's better to download iso from microsoft which have update 1 already installed.
the current Win8.1 ISOs have both Update 1 (KB2919355) and Update 3 (KB3000850) already integrated / slipstreamed.
also try installing fewer updates at a time (aim for less than 30 updates) - installing about 50 or more at the same time can lead to problems.
AND install the recent "rollup" updates last (and separately) and don't install them with the older 8.1 updates
0 -
DAMN IT MICROSOFT! Make up your damn minds about MSE on Win7
Now MS has made complete U-turn about offering MSE definition updates after the Win7 EOL 1/14/2020 date, Vistapocalypse:
Edit: looks like Win7 users will be able to continue to use MSE even after Jan. 14, 2020 - so you can forget about Win7 users seeing any MSE EOL nags, Vistapocalypse. I recently installed the recent MSE definition updates on my bro's Win7 laptop this Dec. 2019 and still no MSE EOL nags appear.
Edit 2: Proof is in this Microsoft community forum thread about extending MSE updates for Win7 after EOL.
1 -
aww crap
now the nags in MSE may be showing up on Win7 as I saw on this blog from Deskmodder.de (when installing recent MSE definition updates in December 2019)
guess it's time for me to remove MSE from any Win7 machines now before Jan. 2020
0 -
well Petr the Intel T2300E processor and other Yonah based processors actually worked on at least the 1903 (May 2019 update) release as I tested this myself several months ago (and of course they'll work with 1909 since that one is basically a 1903 SP1)
it was only the 1809 version that totally broke support for Intel Yonah & Intel Pentium "Dothan" series of CPUs - let's not forget, the 1809 release was rushed by MS in which it first deleted user files upon upgrading to it (when first came out as build 17763.1 back in early Oct. 2018) and got several re-releases after it. MS never figured out how to make 1809 work with these old mobile/laptop PCs, not even with the recent 1809 cumulative updates like KB4523205 released in Nov. 2019 and 1809 refused to boot up with these old laptop CPUs.
Edit: so it seems that support for those old Intel "Dothan" & "Yonah" laptop cpus was restored in the 1903 & 1909 versions. hopefully they may work with the upcoming 20H1/2004 release in 2020.
0 -
On 10/19/2019 at 1:56 AM, Vistapocalypse said:
So you would speculate that MSE 4.10 users running Windows 7 might see a shorter period of nagging before EOL than MSE 4.10 users running Vista did (see MSE For Vista Now Shows XP Nag Screens)? It seems more likely that Microsoft never "upgraded" MSE to extend the EOL time-bomb feature to Windows 7, perhaps in order not to trigger a wave of downgrades to even older MSE versions.
well come back next month in December and ask that original question again, Vistapocalypse.
just manually downloaded & ran the recent mpam-feX64.exe file (11/6) from one of my Win7 machines running MSE 4.10.209 to update the definition files - still not getting any EOL nags from MSE.
only either the KB4493132 or KB4524752 updates for Win7 are showing the EOL nags but no EOL notifications within the MSE app1 -
On 11/5/2019 at 8:10 AM, i430VX said:
I'd recommend using inspectre to disable the meltdown patch after fully updating, it kills win7 performance from my experience
(run it as admin)
https://www.grc.com/inspectre.htmon my family's Win7 system (esp. an old Dell Inspiron PC with an Intel Sandy Bridge i5-2500 cpu), the latest W7 meltdown/spectre patches are doing the opposite, boosting performance rather than degrading/killing it
0 -
On 10/4/2019 at 9:09 AM, Paul75 said:
I meant actually opened a support case. You know MS they will want to charge for any kind of support.
forget about that, Paul75. the chances of MS actually listening to you & others after opening a support case are slim to none when using Office 2010 on XP.
and MS will be ending support for all Office 2010 editions next year on October 2020:
https://docs.microsoft.com/en-us/deployoffice/office-2010-end-support-roadmapso I doubt MS will ever fix the Office 2010 MSO.DLL problems for XP/2003 as Office 2010 will be EOL in less than a year from now
2 -
the Dell Latitude E6330 laptop use IDT High Definition Audio Cocec drivers (IDT audio chip listed is 92HD93) - check the Audio section of the Latitude E6330 downloads page from Dell's web site
btw, IDT sold off their PC audio products to Tempo Semiconductor Inc by end of year 2013 (they got out of the AC97/HDA audio business since they can't keep up with other audio chipset makers like Realtek & VIA)
0 -
On 10/5/2019 at 10:24 AM, VistaLover said:
... More rather a belated release to patch a vulnerability made public in September!
https://borncity.com/win/2019/10/03/internet-explorer-cumulative-update-kb4524135-10-03-2019/
I'd still look out in the Catalog come next Patch Tuesday (Oct 8th 2019) for a newer IE9 cumulative update...
that KB4524135 IE update on 10/3 was an out-of-band update while KB4519974 was the regularly scheduled update on 10/8
On 10/9/2019 at 10:05 AM, Vistapocalypse said:I'm glad to see that someone is still interested enough to post a list of the latest updates. Thank you Kwasiarz. It occurs to me that no one ever posted a list of the September updates. Of course the September rollups have now been superseded anyway, but it might bear repeating that there was a second servicing stack update, KB4517134 , that should be installed before any newer updates.
Nevertheless, it has come to my attention that Microsoft has continued to modify KB4474419, and v4 of the update was posted yesterday.
I have given Vista another chance and installed Vista Business edition 64bit (basically a Vista "Pro") on my mom's old Dell Inspiron laptop on a spare 250gb western digital hard drive this past weekend and will use it until 1/14/2020. I find that installing KB4474419 alone (by itself w/ no other recent updates from April 2019 onward) changes the Vista build number from 6002 to 6003 (as I checked winver.exe and msinfo32.exe apps)
On the other hand, I have the older SHA-2 update (KB4039648 V2) installed that greenhillmaniac mentioned more than a year ago that does not change the Vista 600x build number
0 -
On 9/19/2019 at 5:57 PM, erpdude8 said:
there is a newer servicing stack update (SSU) for Server 2008 - KB4517134. MS support article 4517134 says that this new update supersedes/replaces KB4493730.
gosh damn it Microsoft.
it seems that KB4517134 fails to install if the KB4493730 update is not installed first as I had tested this myself this past weekend (and KB4474419 is also not installed).
so that MS article 4517134 is wrong but on the other hand the MS Update Catalog site about the KB4517134 update is correct that it does not replace KB4493730 [friggin inconsistent info by MS on patch supersedence]I also found that installing the KB4474419 update alone (without installing any other updates from April 2019 & later) changes the build number from 6002 to 6003 and prevents Windows Update from looking for any Vista updates
1 -
-
here's a recent article from ZDNet titled "Why is Windows 10 a mess?"
0 -
On 10/20/2019 at 2:17 AM, Raheem Jamali said:
My roommate has a HP Compaq 6510b laptop with Intel Centrino Duo processor.
what kind of "intel centrino duo" cpu does that computer have, Raheem?
use the CPU-Z tool to identify the exact model of that Intel CPU chip.
0 -
KB3177467 V2 is now obsolete like KB3020369. use KB4490628 or KB4516655 instead [both these updates replace KB3177467 and older servicing stack updates]
very first update to integrate/slipstream is either KB4490628 or KB4516655 as either one is required to install new updates created in Aug. 2019 and later.
0 -
On 10/19/2019 at 2:21 PM, dencorso said: But... but... with all due respect, why on Earth would anyone actually *want* to get either?
I'm sorry I was kinda vague in my previous post.
What I meant to say is that the KB4524752 update will be offered to Win7 Professional users thru Windows Update while those using Home Basic/Premium or Ultimate of Win7 editions will be offered the KB4493132 update instead of KB4524752 on the list of available updates thru WU. And of course neither KB4493132 nor KB4524752 will show up for those using Win7 Enterprise & Server 2008 R2 editions.
2 -
the KB4474419 SHA-2 update for Win7 got another revision in early September 2019 (aka V3)
check out the revisions of KB4474419 on the support article:
https://support.microsoft.com/en-us/help/4474419/sha-2-code-signing-support-update
0 -
Edge 78 went to stable channel a few weeks ago
0 -
KB4524752 is targeted specifically to Win7 PRO users
those using Win7 home premium or ultimate may still get KB4493132 instead
0
But... but... with all due respect, why on Earth would anyone actually *want* to get either? 
Unsupported hardware in 1803 and 1809?
in Windows 10
Posted · Edited by erpdude8
I was wondering Petr, if you still have that old MSI 915GM Speedster-FA4 device, can you try installing 32bit Win10 v1903 or v1909 on there? (using the ISO method - aka install any of those versions from a local usb flash drive or dvd disc). this guy from this Ten forums thread was able to install 1903 on his old 2006 laptop that uses an old Pentium M cpu chip several months ago thru a 1903 ISO and it worked.