Windows 10 (FAQ u drugom postu)

[djalf]

Danas mi se blokirao nacisto, ni mis nije reagovao i samo reset. Sumnjam na Deezer Downloader ili qBittorrent posto dok oni nisu bili ukljuceni nije bilo problema. BIOS nije pomogao.
Da li ce veceras biti neke ispravke?

 

[Dark Magician]

Da nije do SSD? Blast je imao problema takve vrste...

 

[djalf]

Pa da je do njega onda bi i 1709 zezao? Samo April update me zeza.

 

[Dark Magician]

Ume da se pogodi, izašao je patch, probaj. Probaj sa DISM i sfc, ako nisi. Pogledaj event log itd...

 

[djalf]

U logu nema nista, samo da je iznenada reset, nista drugo. Sfc nisam a i ne sumnjam jer se isto ponasao i sa clean install. Sta je DISM? Inace 1709 mi je radio savrseno.
Nisam pri racunaru, el izasao patch? Obicno je posle 19h po nasem vremenu.

 

[Dark Magician]

Tačno u 19h po našem vremenu se pušta.

Za 1803 changelog

Addresses an issue with the April 2018 Windows Servicing update that causes App-V Scripts (User Scripts) to stop working.
Addresses an issue that prevents certain VPN apps from working on builds of Windows 10, version 1803. These apps were developed using an SDK version that precedes Windows 10, version 1803, and use the public RasSetEntryProperties API.
Addresses additional issues with updated time zone information.
Addresses an issue that may cause an error when connecting to a Remote Desktop server. For more information, see CredSSP updates for CVE-2018-0886.
Security updates to Windows Server, Microsoft Edge, Internet Explorer, Microsoft scripting engine, Windows app platform and frameworks, Windows kernel, Microsoft Graphics Component, Windows storage and filesystems, HTML help, and Windows Hyper-V.

Komanda, slična sfc, kao admin: DISM /Online /Cleanup-Image /RestoreHealth

 

[djalf]

Pustam ga ujutru pa javljam rezultat. Hvala za komandu.

 

[Dark Magician]

U krajnjem slučaju, ako ne nađeš rešenje/uzrok vrati se na 1709, pa za mesec, dva pređi.

 

[The Lyricist]

Da li koristi neko Chrome od vas kome se ne blokira? Sad mi se opet blokirao ali sam uspeo da ga odblokiram sa kombinacijom tastera Windows logo key + Ctrl + Shift + B i nije morao restart, sto je bar neko resenje do ispravke. Naravno moracu da predjem na Firefox. 360 AV dakle nije uzrok.

restartovao se nocas, sam digao chrome sa svim sto je bilo na nj, doduse, pobio sam mu brda tabova, al' napunice se to za koj sat.
redovno apdejtovan, takodje, bez ikakvih problema. (masina/sistem su stari nesto manje od godinu dana but still)

 

[djalf]

Izgleda da sam samo ja nesrecnik sa problemom
Odradio update i sfc /scannow, rezultat kaze: "Windows Resource Protection did not find any integrity violations."
Sad ide test pa javljam ima li promene.

@Dark Magician
Nije problem da se vratim na 1709 ali je problem ako ljudima stavim 1803 i budu imali problema. Za sad sam stavio na 3 racunara, videcemo da li ce oni imati probleme kao ja.

 

[Dark Magician]

nVidia drajver može da bude problem, uradi clean reinstall sa najnovijim, ako nisi.

Za probleme je diskutabilno, kod mene su četiri na 1803, bez problema, što ne znači da bi na petom radilo.

 

[djalf]

Nisam ispravio opis racunara, GTX je kod klinca a ja koristim HD 610 iz procesora. Za sad se nije blokirao posle update-a, nadam se da je reseno ali videcemo do kraja dana. Juce se blokirao 2 puta do ovog vremena.

 

[Running]

S' vremena na vrijeme pocnu da se pojavljuju i trepere neka crna polja po browseru. Nije ovoga bilo prije upgrade-a. Sta je u pitanju, ima li rjesenja!?

 

[Dark Magician]

Grafički drajveri moguće (reinstaliraj/instaliraj najnovije), probaj drugi browser.
Chrome je u pitanju?

 

[keza]

S' vremena na vrijeme pocnu da se pojavljuju i trepere neka crna polja po browseru. Nije ovoga bilo prije upgrade-a. Sta je u pitanju, ima li rjesenja!?

Ovo se i meni dešava posle updatea, imam Intelovu integrisanu grafičku.

 

[djalf]

Meni juce nije blokirao, tako da mozemo da kazemo da je to reseno update-om.

 

[Running]

Ovo se i meni dešava posle updatea, imam Intelovu integrisanu grafičku.

I kod mene je intel i nvidia posebno, laptop je, ali integrisanu stalno koristi. Pogledacu bas ima li novijih drajvera, mada sam skoro bio trazio. Takodje i animacije kad se zatvaraju prozori nekad baguju, kad se iskljuce ok je (animacije za min i max-imiziranje windows-a).

Sent from my Nexus 6 using Tapatalk

 

[Šumadinac]

Prvi problem sa Windows 10 OS
Kupio da promenim bežičnu karticu u laptopu jer ne može da izvuče 150/8 mbps SBB paket (ide samo do 50).
Ovo javlja:

Kartica ima najnovije drajvere za windows 10 - https://downloadcenter.intel.com/product/75439/Intel-Dual-Band-Wireless-AC-7260

Stavio sam na flash Ubuntu 18.04 LTS amd64 - live bez instalacije i kartica radi najnormalnije

Kada proguglam "Intel AC 7260 This device cannot start (Code 10)" ima dosta rezultata ...
Ima li neko ideju kako srediti ovo?

 

[Running]

Grafički drajveri moguće (reinstaliraj/instaliraj najnovije), probaj drugi browser.
Chrome je u pitanju?

Ovo se i meni dešava posle updatea, imam Intelovu integrisanu grafičku.

Izgleda da su drajveri rijesili stvar i sa animacijama onim sto su bugovale i sa chromeom. Samo sto je morala biti forsirana instalacija (ono have disk-inf), jer je setup javljao da nije 'validated' za moj notebook. U Readme! pise da podrzava sve OK. Tacno treba malo osvjeziti drajvere i to sa sajta proizvodjaca komponenata, barem one vitalne, oni sa sajta proizvodjaca laptopa su odavno zastarili.

Ovo je isto dobar sajt, moze se naci svasta korisno vezano za drajvere.

https://www.catalog.update.microsoft.com

 

[Dark Magician]

Prvi problem sa Windows 10 OS
Kupio da promenim bežičnu karticu u laptopu jer ne može da izvuče 150/8 mbps SBB paket (ide samo do 50).
Ovo javlja:

Kartica ima najnovije drajvere za windows 10 - https://downloadcenter.intel.com/product/75439/Intel-Dual-Band-Wireless-AC-7260

Stavio sam na flash Ubuntu 18.04 LTS amd64 - live bez instalacije i kartica radi najnormalnije

Kada proguglam "Intel AC 7260 This device cannot start (Code 10)" ima dosta rezultata ...
Ima li neko ideju kako srediti ovo?

Šta piše u tom logu? I da li imaš neki AV, da nije blokirao nešto oko instalacije drajvera?

 

[mihajlosd]

Odradio update u sredu i evo ga zapucao se na onom krugu što vrti kod učitavanja. Ja ga pustio reko možda će potrajati, medjutim pola dana tako i nista. Šta da mu radim?

Sent from my Passport using Tapatalk

 

[Dark Magician]

Je li završio update, pa posle neće, ili nikako da ga završi?
Ako je prvo pokušaj da uđeš u safe mode, ako je drugo, restartuje trebalo bi da automatski pokrene da vrati na stariju verziju.
Imaš li AV koji nije Defender ili OC?

 

[Šumadinac]

Šta piše u tom logu? I da li imaš neki AV, da nije blokirao nešto oko instalacije drajvera?

Nemam, problem je vrlo složen i prisutan samo windows-u.
Bios/drajveri/windows/MS/Intel svi su pomalo krivi - pun internet istih pitanja oko intel bežičnih kartica!

Na ubuntu live instalaciji radi trenutno bez ikakvih čačkanja

 

[Sasa012]

 

[Deleted member 46590]

Samo nam još i to fali.

 

[djalf]

Odradio update u sredu i evo ga zapucao se na onom krugu što vrti kod učitavanja. Ja ga pustio reko možda će potrajati, medjutim pola dana tako i nista. Šta da mu radim?

Da li si uradio restart posle update-a? Kad se zaglavi probaj kombinaciju tastera Windows key + Ctrl + Shift + B taster. Meni je tako odglavio skoro svaki put a posle update-a nemam vise tih problema.

 

[sam633]

M$ u epizodi:"Kako se pokakiti na samog sebe".

Surface Pro (2017) owners hitting Win10 1803 update blue screens. Now we know why.

As Win10 version 1803 rattles through the unpaid beta-testing phase, it’s snagged another victim — Intel’s aging SSD6 solid-state drives. Both Microsoft and Intel now admit that running Win10 version 1803 on Intel 600p or Pro 6000p is a recipe for disaster.

Some Surface Pro (2017) models ship with “bad” Intel SSD Pro 6000p drives. Customers are complaining about freezes with Win10 version 1803 — and the Microsoft support folks don’t have a clue what’s causing the problem. Now we know.

Here’s how the drama unfolded.

Win10 version 1803 has been in beta testing for centuries, in internet time. The “final” version, build 17134.1, entered the Windows Insider Fast ring almost a month ago, on April 16. In a jumble of mixed-up build numbers, Win10 version 1803 has been officially pushed since April 30. Why did it take so long to figure out that the 600p and Pro 6000p cause problems?

Surely somebody at Microsoft and some other body at Intel must be testing these things, right? Shirley.

Some Surface Pro (2017) computers ship with Intel SSD Pro 6000p drives. Shirley somebody at Microsoft tested those, too, didn’t they?

It's hard for me to imagine Microsoft shipping the new version of Win10 without testing it on the latest Surface Pro 2017 devices. I mean, c'mon. We aren't talking rocket science here.

I first heard about the problem on May 7, when a “Microsoft Agent” (love that term) named Lonnie_L posted on the MS Answers forum:

When attempting to upgrade to Window 10 April 2018 Update select devices with certain Intel SSDs may enter a UEFI screen reboot or crash repeatedly.

Microsoft is currently blocking some Intel SSDs from installing the April 2018 Update due to a known incompatibility that may cause performance and stability issues. There is no workaround for this issue. If you have encountered this issue, you can roll back to Windows 10, version 1709 and wait for the resolution before attempting to install the April 2018 Update again.

Microsoft is currently working on a solution that will be provided in a near future Windows Update, after which these devices will be able to install the April 2018 Update

Yesterday, May 10, I received a nudge from a Microsoft PR person, pointing to the same Answers forum post. It’s been modified to say:

When attempting to upgrade to the Windows 10 April 2018 Update, select devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series may crash and enter a UEFI screen after reboot.

Microsoft is working with OEM partners and Intel to identify and block devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series from installing the April 2018 Update due to a know incompatibility that may cause performance and stability issues. If you have encountered this issue, follow the steps to reinstall the previous operating system (Windows 10, version 1709).

Microsoft is currently working on a resolution that will allow the April 2018 Update on these devices in the near future.

Looking at the post, you’d have no way to know when or how it was modified. Commenting on the topic has always been shut off. See how that works?

So now we know that the 600p SSDs don’t like Win10 version 1803. It took Microsoft eight days to acknowledge the problem, and two more days to spill the beans about which drives aren’t copacetic.

But the drama doesn't stop there. Surface Pro (2017) owners have been complaining about blue screens when they try to upgrade to Win10 version 1803. For example, on May 6, eljeffe58 posted this on the MS Answers forum:

I just got a SP 2017 at Best Buy. I returned the first one cuz after she updated to build 1803 I could not escape BSOD's. I returned her after a few days and the new one has the same thing. I restored back to the 1709 she came with and will try not to let her update until a new update supersedes the 1803 mess. I also could not get the update downloads to easily complete without running the fix it troubleshooter and/or just rebooting. A real mess if you ask me. I love the SP 2017 but hate the updates and really hate a BSOD at work in the middle of helping a client.. Thanks.

Later in the thread, eljeffe58 says his brand-spanking-new Surface Pro 2017 has an . Intel SSDPEBKF128G7 SSD. BCVHOG says he has an SSDPEBKF256G7. Both of those model numbers are Intel Pro 6000p SSDs.

That’s not the worst of it. Microsoft’s tech support on that thread hasn’t helped one whit. On May 9, eljeffe58 reports that he received a Service Request number from Microsoft Surface Technical Support about “the BSOD that the Surface devices with i5 processor are experiencing with the new Windows version 1803.”

You don’t say.

At least the bug notification now appears on the official build 17134.48 page. Wonder when that was changed?

 

[mihajlosd]

Je li završio update, pa posle neće, ili nikako da ga završi?
Ako je prvo pokušaj da uđeš u safe mode, ako je drugo, restartuje trebalo bi da automatski pokrene da vrati na stariju verziju.
Imaš li AV koji nije Defender ili OC?

Završio update i tražio restart...klasika. I onda krenuo da se butuje i butuje i butuje...I nikad kraja.

Da li si uradio restart posle update-a? Kad se zaglavi probaj kombinaciju tastera Windows key + Ctrl + Shift + B taster. Meni je tako odglavio skoro svaki put a posle update-a nemam vise tih problema.

Probaću sutra što ste mi predložili pa da vidim. Ne znam koj mu je vrag...

Sent from my Passport using Tapatalk

 

[Lukija]

Uradio update na dve masine. Na jednoj sam dobijao BSOD na 15% instalacije (HP masina, nista OC). Na kraju uradio reinstall celog sistema i potrosio. Potrosio 3 dana. Na drugoj masini sve proslo OK osim sto Night light radi kako njemu dune. Lepo kaze nas narod, od g0vneta ne mozes napraviti pitu.

 

[Drakenzen]

Ne stvarno je ovaj win 10 tolika lakrdija da to nema smisla, ubijaju sa ovim updejtovima kao da nisu normalni, non stop komp radi nesto u pozadini i iskreno da vam kazem da se nisam navikao na start meni i na integrisan sistem obavestenja za aplikaciije, sutra bih se cratio na win7

Sent from my Note 8