Announcing Windows 10 Insider Preview Build 14291 for PC and Mobile Insider

Joanne said:

Okay, time for my report for this new Insider Preview build...because...for reasons completely inexplicable to me this time the entire thing went nuts..............

A couple of days ago I clean installed version 1511 and after the updates I brought it to version 10586.164
I logged in with my MS account and waited for the Insider build to appear. It finally arrived and I upgraded.

From some earlier posts it appears you are alternating between the normal commercial build of Windows (10586.164) and Fast Lane Insider builds like 14291. I'm not clear on why you are doing this, but if you want to avoid bugs and just use Windows stay with 10586 until the next official build release--that's my advice for what it's worth.

- SFC /SCANNOW does not function! "Windows Resource Protection Could Not Start the Repair Service", it says! Yes, I have made sure that the Windows Modules Installer service is enabled and set to Manual.

This is a bug introduced at least one build back from the present Insider build 14291. If you want to fix it, here's how (I found this in another Win10 forum, used it, and found that it works perfectly):

create a text file by right-clicking on your desktop and selecting New/Text document, and copy & paste the following into it:

@echo off
cls
setlocal
set root=%SystemRoot%\WinSxS\%PROCESSOR_ARCHITECTURE%_microsoft-windows-servicingstack
for /f "delims=" %%A in ('dir /ad /b %root%-onecore*') do set "from=%SystemRoot%\WinSxS\%%A"
for /f "delims=" %%A in ('dir /ad /b %root%_*') do set "to=%SystemRoot%\WinSxS\%%A"
takeown /F %to%\* /R /A 1>nul
icacls %to%\*.* /T /grant administrators:F 1>nul
echo on
echo F|xcopy /C /R /O /Y %from%\wrpint.dll %to%\wrpint.dll
pause

-save the text file

-then rename your text file to something like "RepairSFC.cmd", taking care to replace ".txt" with ".cmd"

-right-click on RepairSFC.cmd and select the "Run as Adminstrator" option

-the commands will run and repair the bug and SFC should immediately function thereafter.

In summary, unless you enjoy bugs to some extent, you should stay with the commercially released build of Windows 10586...

I've been quoted quite a few times and some people have referred to my post on this thread so I'd like to clarify the following:

1) I am dual booting between my primary (main) OS which is Windows 10 Pro build 10586.164 and the latest Insider Preview build available at the present point in time. I am using two separate SSDs for this purpose, the SanDisk from my system specs always containing my primary OS and the Samsung SSD always used for the current Insider build. I always perform a clean installation of the operating systems, with the respective drive being the only drive connected to my system during installation. My primary OS functions perfectly and that's why I'm using it.

2) I am not a native English speaker so I am not 100% sure about how "harsh" some of the words I've used a couple of posts ago have sounded and IF I've hurt the feelings of some people... Personally, I do not consider "vulgar" the way I have expressed myself and since we all have the right of Freedom of Speech, I think I have expressed myself correctly. Personally, I consider that I have just reported a few new issues. Perhaps I did it in an "exaggerated" manner but it was indeed a surprise for me to discover these new issues together with the rest I had.

3) I'd like to thank pbcopter for the SFC - bug solution he/she gave in post #144. I like problem solvers and solution providers.

Thank you.

Edwin said:

Eliminating secondary monitors eliminated the crashing snipping tools issue, but, that's not acceptable!

blutos cousin said:

Right that's a bummer :
That's interesting I have a 4K Sony HDR TV connected to my d/GPU as a second (extended desktop ) screen on an HDMI cable ofc.
The TV been on when Snip tool been crashing but not on the PC input but more than likely the EDID stuff been going on anyway because I've been changing some of the TV HDMI inputs and Android TV apps and OTA with the remote .

Well, another secondary monitor and another Sniping tool problem.
Well done Edwin, at least we know now where the problem is.

Staying away from Snip for now. I'm not going to install some third party solution, just using Printscreen and crop the picture.

Also a bit higher memory usage than previous builds. But not a problem really.

I been testing this build for about 1 hour and so far haven't had problems. I see when you hoover your mouse cursor over clock in the right hand corner a popup tells you the local time and the Pacific time. A neat little feature. Does anyone know if you can set what time zone it shows?

Just found out you can change what time zone it shows. Right click on the clock. Click Adjust date/time, then click Add clocks for different time zones.

Joanne said:

I've been quoted quite a few times and some people have referred to my post on this thread so I'd like to clarify the following:

1) I am dual booting between my primary (main) OS which is Windows 10 Pro build 10586.164 and the latest Insider Preview build available at the present point in time. I am using two separate SSDs for this purpose, the SanDisk from my system specs always containing my primary OS and the Samsung SSD always used for the current Insider build. I always perform a clean installation of the operating systems, with the respective drive being the only drive connected to my system during installation. My primary OS functions perfectly and that's why I'm using it.

2) I am not a native English speaker so I am not 100% sure about how "harsh" some of the words I've used a couple of posts ago have sounded and IF I've hurt the feelings of some people... Personally, I do not consider "vulgar" the way I have expressed myself and since we all have the right of Freedom of Speech, I think I have expressed myself correctly. Personally, I consider that I have just reported a few new issues. Perhaps I did it in an "exaggerated" manner but it was indeed a surprise for me to discover these new issues together with the rest I had.

3) I'd like to thank pbcopter for the SFC - bug solution he/she gave in post #144. I like problem solvers and solution providers.

Thank you.

I am replying to back you up. I'm darned if I saw anything 'wrong' with your post and find it unfortunate you felt you needed to defend yourself.

As a 'native English speaker' there is no way I could tell you weren't! That, certainly, is nothing to apologize for, either. I really admire the very many people who do so well with English as their second language.

So, Joanne, kia kaha (Maori for stay strong).

Winuser said:

I been testing this build for about 1 hour and so far haven't had problems. I see when you hoover your mouse cursor over clock in the right hand corner a popup tells you the local time and the Pacific time. A neat little feature. Does anyone know if you can set what time zone it shows?

I didn't have much wrong the first day I was thinking it was way cool ... ,it went to H. in a handbasket since then........ don't let it fool you or be your primary OS system

Winuser said:

Just found out you can change what time zone it shows. Right click on the clock. Click Adjust date/time, then click Add clocks for different time zones.

edit..... s***** mine won't do that you left click on the date time setting link and it opens up the setting app for all that like it been doing