Offizieller Windows-Thread

[Byakuya]

AGP wird's wohl kaum noch sein.
Wenn du keine mega GraKa einbauen willst die zusätzliche Power Pins benötigt sollte alles sicher sein

 

[PS3Man]

Ich würde da eher auf das Netzteil tippen das da wohl langsam den Geist aufgibt. Grafikkartendefekt glaube ich eher nicht, da gibts normalerweise Bildfehler.

 

[crack-king]

Wer weiß, Möglichkeiten das nachzuvollziehen habe ich eh nicht...

Unterm Strich würde denen auch ein Tablet reichen. Mehr machen die da auch nicht.

---------- Beitrag um 18:55 Uhr hinzugefügt ---------- Vorheriger Beitrag um 18:54 Uhr ----------

AGP wird's wohl kaum noch sein.
Wenn du keine mega GraKa einbauen willst die zusätzliche Power Pins benötigt sollte alles sicher sein

Wenn, dann würde ich eh die billigste einbauen, die ich finden kann

 

[crysmopompas]

Könnte mir vorstellen, dass der Stromverbrauch dadurch sinkt.

Ja, wird deutlich sparsamer sein.

Ich weiß ja nicht wie intensiv der Rechenr genutzt wird.

Passen die aktuellen Grafikkarten eigentlich in so ein altes Ding oder könnte es da Probleme geben?

Sollte kein Problem sein wenn ein entsprechender PCIe Slot vorhanden ist.
Sparsames Modell ohne extra Stromanschluß wählen.

Treiber für Windows 7 gibt's glaube ich noch von allen Herstellern außer Intel, aber nochmal prüfen.

AMD hat Win 8.1 Treiber eingestellt .



Nvidia stellt 32Bit Support ein.
http://nvidia.custhelp.com/app/answ...a-driver-support-for-32-bit-operating-systems

After Release 390, NVIDIA will no longer release drivers for 32-bit operating systems1 for any GPU architecture. Later driver release versions will not operate, nor install, on 32-bit operating systems. Driver enhancements, driver optimizations, and operating system features in driver versions after Release 390 will not be incorporated back into Release 390 or earlier versions. This impacts the following operating systems:

• Microsoft Windows 7
• Microsoft Windows 8/8.1
• Microsoft Windows 10
• Linux
• FreeBSD

NVIDIA intends to support critical driver security fixes until January 2019. For more details on product security, see http://www.nvidia.com/security.

RIP NTVDM

 

[mojo]

hast du einfach mal verscuht den Treiber neu zu installieren?

 

[crysmopompas]

Understanding the performance impact of Spectre and Meltdown mitigations on Windows Systems

In general, our experience is that Variant 1 and Variant 3 mitigations have minimal performance impact, while Variant 2 remediation, including OS and microcode, has a performance impact.

Here is the summary of what we have found so far:

• With Windows 10 on newer silicon (2016-era PCs with Skylake, Kabylake or newer CPU), benchmarks show single-digit slowdowns, but we don’t expect most users to notice a change because these percentages are reflected in milliseconds.
• With Windows 10 on older silicon (2015-era PCs with Haswell or older CPU), some benchmarks show more significant slowdowns, and we expect that some users will notice a decrease in system performance.
• With Windows 8 and Windows 7 on older silicon (2015-era PCs with Haswell or older CPU), we expect most users to notice a decrease in system performance.
• Windows Server on any silicon, especially in any IO-intensive application, shows a more significant performance impact when you enable the mitigations to isolate untrusted code within a Windows Server instance. This is why you want to be careful to evaluate the risk of untrusted code for each Windows Server instance, and balance the security versus performance tradeoff for your environment.

Auf CPUs von 2015 und früher erwartet MS, daß die meisten User unter Windows 7/8 Performanceeinbußen feststellen!
Das ist mal eine Ansage.

Hier muß ein möglichst einfacher Schalter in's OS um den User entscheiden zu lassen was er will.
Sonst kann man nur noch alle Updates abschalten oder deinstallieren. Geht bei W7/8 zum Glück noch einfach.

For context, on newer CPUs such as on Skylake and beyond, Intel has refined the instructions used to disable branch speculation to be more specific to indirect branches, reducing the overall performance penalty of the Spectre mitigation. Older versions of Windows have a larger performance impact because Windows 7 and Windows 8 have more user-kernel transitions because of legacy design decisions, such as all font rendering taking place in the kernel. We will publish data on benchmark performance in the weeks ahead.

---------- Beitrag um 21:17 Uhr hinzugefügt ---------- Vorheriger Beitrag um 21:03 Uhr ----------



[ame]https://twitter.com/aaron_coltrane/status/947512273811030016[/ame]
[ame]https://twitter.com/jaymelbe/status/948114416364654592[/ame]
[ame]https://twitter.com/videolan/status/948171613568229376[/ame]

 

[Planet]

Nein, das ist keine gute Idee. Die meisten Benutzer verstehen die technischen Zusammenhänge nicht, und er eine oder andere Dummkopf (sprich: Millionen) würde dann denken: was soll mir schon passieren? Und kriegt man von Patches nicht sowieso irgendwann Hautkrebs? Besser nicht...

 

[crysmopompas]

Seit wann arbeitest du bei Apple?

Am besten wäre es immer noch Intel schickt mir neue CPUs - nur dumm wenn die verlötet sind

 

[crysmopompas]

We will not be issuing updates for Windows Vista or Windows XP-based systems including WES 2009 and POSReady 2009.

https://support.microsoft.com/en-us...your-windows-devices-against-spectre-meltdown

Die letzten beiden haben noch offiz. Support.

 

[mojo]

Meltdown patch fickt shadowing in 2012 R2 und 2016 RDS Umgebungen.

https://social.technet.microsoft.co...-kb4056890-breaks-shadowing?forum=winserverTS

 

[crysmopompas]

Benchmarks mit aktueller CPU + W10

https://www.techspot.com/article/1556-meltdown-and-spectre-cpu-performance-windows/

---------- Beitrag um 23:33 Uhr hinzugefügt ---------- Vorheriger Beitrag um 23:17 Uhr ----------

Bei Server ist es richtig gemacht: Registrysettings für die Fixes.
Bitte auch für Desktop.

https://support.microsoft.com/en-us...-to-protect-against-the-speculative-execution

Für 2008 und 2012 gibt es aktuell keine Patches.


Was ist dieses Shadowing?

 

[mojo]

User Sessions Spiegeln um nicht vor Ort zu müssen.


Oh boi. Intel zieht Microcode Updates zurück.

lenovo:

Withdrawn CPU Microcode Updates: Intel provides to Lenovo the CPU microcode updates required to address Variant 2, which Lenovo then incorporates into BIOS/UEFI firmware. Intel recently notified Lenovo of quality issues in two of these microcode updates, and concerns about one more. These are marked in the product tables with “Earlier update X withdrawn by Intel” and a footnote reference to one of the following: *1 – (Kaby Lake U/Y, U23e, H/S/X) Symptom: Intermittent system hang during system sleep (S3) cycling. If you have already applied the firmware update and experience hangs during sleep/wake, please flash back to the previous BIOS/UEFI level, or disable sleep (S3) mode on your system; and then apply the improved update when it becomes available. If you have not already applied the update, please wait until the improved firmware level is available. *2 – (Broadwell E) Symptom: Intermittent blue screen during system restart. If you have already applied the update, Intel suggests continuing to use the firmware level until an improved one is available. If you have not applied the update, please wait until the improved firmware level is available. *3 – (Broadwell E, H, U/Y; Haswell standard, Core Extreme, ULT) Symptom: Intel has received reports of unexpected page faults, which they are currently investigating. Out of an abundance of caution, Intel requested Lenovo to stop distributing this firmware.

https://support.lenovo.com/de/de/solutions/len-18282

dell ebenso

NOTE 1: 13G, select 12G, and select DSS server BIOS files have been pulled from http://dell.com/support. This note and article will be updated as soon as more information is available.

http://www.dell.com/support/article...prise-servers-storage-and-networking-?lang=en



flashe ich nun wieder zurück? Wann ist mit dem korrekten Update zu rechnen? Oh man.


was für eine Shitshow diese ganze Aktion.

 

[mW2fast4u]

shadowing kannte ich gar nicht, eher Interessant bei RDS Farmen.

schon alles geflasht?
Junge, abwarten und tee trinken
bei uns hat erstmal jeder applicationhersteller angeklopft, eh keine Updates installieren, sonst läuft die Anwendung nicht mehr.

 

[mojo]

ja ich betreibe 2 RDS Collections mit 16 Hosts für 600 User. darf unser Usersupport eben die Turnschuhe wieder auspacken.

ich habe jedenfalls meine HyperV Cluster geflasht.
8 mal Dell R730
da die bugs aber wohl nur S3 state und boot betreffen werde ich es erstmal so lassen und auf ein schnelles update hoffen.

 

[crysmopompas]

RIP PowerShell
(basiert auf .NET, wird nicht mehr weiterentwickelt)


Welcome Powershell Core
(basiert auf .NET Core)



https://blogs.msdn.microsoft.com/po...ore-6-0-generally-available-ga-and-supported/

there are currently no plans to introduce new functionality to Windows PowerShell. This means that the risk of regression will be very low for Windows PowerShell, so you can count on it as a stable platform for your existing workloads. There are also no plans to provide a new Windows Management Framework (WMF) package for downlevel operating systems.

PowerShell Core is adopting the Microsoft Modern Lifecycle Policy, a new support lifecycle intended to keep customers up-to-date with the latest versions.

d.h.immer nur die gerade neueste Version von PS Core ist unterstützt.

User Sessions Spiegeln um nicht vor Ort zu müssen.

Als sowas wie "Remoteunterstützung" am Desktop.

 

[mojo]

Als sowas wie "Remoteunterstützung" am Desktop.

im Grunde ja.

 

[Planet]

Fefe hat einen interessanten Artikel verlinkt: What Really Happened with Vista: An Insider’s Retrospective

In many cases, these security changes meant deep architectural changes were required to third party solutions. And most ecosystem vendors were not incented to invest heavily in their legacy apps. Some of these solutions took the unorthodox approach of modifying data structures and even instructions in the kernel in order to implement their functionality, bypassing APIs and multiprocessor locks that often caused havoc. Antivirus vendors were notorious for using this approach.

In my role as the head of Microsoft security, I personally spent many years explaining to antivirus vendors why we would no longer allow them to “patch” kernel instructions and data structures in memory, why this was a security risk, and why they needed to use approved APIs going forward, that we would no longer support their legacy apps with deep hooks in the Windows kernel — the same ones that hackers were using to attack consumer systems. Our “friends”, the antivirus vendors, turned around and sued us, claiming we were blocking their livelihood and abusing our monopoly power! With friends like that, who needs enemies? They just wanted their old solutions to keep working even if that meant reducing the security of our mutual customer — the very thing they were supposed to be improving.

Anti-Virus ist wohl analog zu Anti-Terror.

 

[crysmopompas]

Das Zitierte ist soweit bekannt. Gab es nicht erst mit XP SP2 eine offizielle API für Virenscanner? Vorher blieb also nichts anderes übrig als Kernelhacking.
Später hat MS dann "Hacks" in Windows immer mehr eingeschränkt, so kam z.B. auch ein Signaturzwang für Treiber. Das ganze hat immer zwei Seiten, "Sicherheit" vs Freiheit&Innovation.

Mich hat daher im Zusammenhang mit dem Meltdownupdate schon gewundert, daß AV Hersteller immer noch am Kernel drehen (dürfen).

Werde jetzt mal den ganzen Artikel lesen.
Dieser interessante Artikel von einem ehem. MS Office Mitarbeiter ist in ihm verlinkt:

What Really Happened with Vista
https://hackernoon.com/what-really-happened-with-vista-4ca7ffb5a1a

I apologize for the length. The TL;DR; version is:

• Microsoft badly misjudged the underlying trends in computer hardware, in particular the right turn that occurred in 2003 to the trend of rapid improvements in single-threaded processor speed and matching improvements in other core elements of the PC. Vista was planned for and built for hardware that did not exist. This was bad for desktops, worse for laptops and disastrous for mobile.
• The bet on C# and managed code was poorly motivated and poorly executed. This failure in particular can be laid directly on Bill Gates and his fruitless Holy Grail effort to create a universal storage and universal canvas applications infrastructure. This had especially long-running consequences.
• Windows project management had teetered on catastrophic throughout its history with a trail of late projects that stumbled to completion. Vista was a disaster but was just the culmination of a series of near-catastrophes in the core executive mission of complex project execution.

The bet on C# and managed code included a strategy that reduced investments in the core unmanaged Win32 layers. I remember long meetings trying to get Windows to commit to relatively minor investments in text and graphics features that Office needed. Pulling these C# components out of the release made it even more obvious that Windows would be going years with very little improvement in core user interface controls for developers (like Office) on their main Win32 API.

Das hält leider bis heute an.
Immer wieder wurde/wird versucht Managed Code zu pushen.
.NET (alte .NET Programme laufen im Gegensatz zu den meisten Win32 Programmen bereits nicht mehr auf neueren Windowsversionen), Win8 RT, Silverlight, Win10 RT, .NET Core.
Wer sein Geld nicht in die Tonne werfen will hat hoffentlich immer an Win32 festgehalten.

Oder baut jetzt alles als Browser-Bloat (Chromium embedded) :sick:

The accusations of bloat I have made against the managed C# stack clearly does not explain the challenges with Vista performance since the managed layers were pushed out of the release. Windows XP shipped with a minimum system requirement of 64MB of memory, raised to 128MB in the major Windows XP security service pack. Vista increased the memory requirements to 512MB, although realistically required up to 1GB to run well (older readers will remember the scandal of questionably labeled “Vista Capable” computers). There is no single explanation for the increase in requirements. There were lots of individual teams that looked to take advantage of “inevitable” increases in performance due to Moore’s Law and the cumulative effect was this bloat. In fact, an important factor in this overall performance cost (and the overall quality issues) was the race to shipping that happened at the end of the release. Performance results come from big decisions but often comes from many small decisions and small improvements made by long hours spent analyzing code, driving results and balancing costs and benefits. That time simply was not available. The improvements made in Windows 7 clearly demonstrated that the opportunity was there — but not the time.

Vista hat auch ohne die geplanten "managed layers" viele neue Layer und Dienste hinzugefügt. Manches für Sicherheit + Kompatibilität. Dann ein vollkommen neues (gepuffertes) Grafiksystem.
Danach hat MS versucht das zu optimieren. Der Höhepunkt ist imo Windows 8 (von dem neu eingeführten App-Zeugs mal abgesehen), das sollte schließlich auch gut auf einfachen mobilen Geräten laufen. Seit Windows 10 steigt der Bloat wieder an (Rechner haben jetzt mehr RAM, SSDs werden gefühlt als Standard angenommen, und mittlerweile kann man Mobile auch vergessen)

The basic use cases — productivity (mostly Office), communications, browsing (including search, web sites and web applications), custom internal line-of-business applications, front ends to custom devices (think of your dentist’s x-ray machine) had mostly stabilized by 2000 and have not changed much since then. Microsoft could continue building new APIs but mostly the devices already did what users needed. The improvements desired by users — better manageability, stability, performance, security on the software side and longer battery life, lighter weight, faster processors, faster communications, bigger screens on the hardware side in many cases needed less software, not more.

 

[mojo]

https://skyfallattack.com

it begins

---------- Beitrag um 11:27 Uhr hinzugefügt ---------- Vorheriger Beitrag um 11:25 Uhr ----------

oder auch nicht

[ame]https://twitter.com/TheRegister/status/954065341713235973[/ame]

 

[crysmopompas]

[ame]https://twitter.com/h0x0d/status/956357544850550784[/ame]