MagicAndre1981

the application throws an exception while detecting the TEMP folder lpksetup!GetUniqueTempPath PRIMARY_PROBLEM_CLASS: STATUS_FATAL_APP_EXITBUGCHECK_STR: APPLICATION_FAULT_STATUS_FATAL_APP_EXITSTACK_TEXT: 00000000`014af770 000007fe`fcd5940d kernelbase!RaiseException+0x3900000000`014af840 000007fe`feaba947 msvcrt!CxxThrowException+0x8700000000`014af8b0 00000000`ffde2c28 lpksetup!GetUniqueTempPath+0x9800000000`014afb80 00000000`ffdc1e8c lpksetup!CbsSession::open_package+0x9000000000`014afc40 00000000`ffdc35c1 lpksetup!CbsClient::EnumerateInstalledLanguagePacksImpl+0x18100000000`014afd60 00000000`ffdc2480 lpksetup!CbsClientServerImpl+0x26c00000000`014afe00 00000000`76b859ed kernel32!BaseThreadInitThunk+0xd00000000`014afe30 00000000`76dbc541 ntdll!RtlUserThreadStart+0x1dFOLLOWUP_IP: lpksetup!GetUniqueTempPath+9800000000`ffde2c28 90 nopSYMBOL_NAME: lpksetup!GetUniqueTempPath+98IMAGE_NAME: lpksetup.exeFAILURE_BUCKET_ID: STATUS_FATAL_APP_EXIT_40000015_lpksetup.exe!GetUniqueTempPathI see this string: B:\TEMP\lpksetup Is B:\Temp a valid path?

why are you not using StartIsBack+?

I sent a feature request to Mark. Maybe he implements and easy show of the attached device in an update to Process Explorer.

This argument is silly, not UAC. But I gave it up. I'll stop this discussion. You're not willing to accept valid arguments.

create a crash dump: http://msdn.microsoft.com/en-us/library/bb787181%28VS.85%29.aspx and share it

again, the UAC is NO block list feature to see which program is safe. Read my guide. @Noel sorry your post shows you have no idea about anything. And you are a developer? So you don't care about permissions in your tools and write to C:\Program Files?

UAC has nothing to do with being a strong/increased security feature. It is a UX feature. When you run an action, which requires admin rights, you get an error message (Access denied). So you have to switch to an account which has admin rights and run it again. This is pure horror. UAC helps you here. You can with standard user rights and when you need admin rights you only have to approve them. This is large UX IMPROVEMENT! Read my UAC tutorial here on msfn.

I need someone who replies to my Guides (Win7/8 boot trace, DPC). The replies from yesterday haven't triggered notification.

the reason is to make apps secure by running them in a sandbox (low IL) and this requires UAC. UAC is great and everyone who disables UAC doesn't understand it.

try to capture a trace with this command: xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER+LATENCY+DISK_IO_INIT+DISPATCHER+FILE_IO+FILENAME -stackwalk profile+CSwitch+ReadyThread+DiskReadInit+DiskWriteInit -resultPath C:\TEMP zip the trace, upload it and send me the link.

I also no longer get notification and I haven't changed anything.

updates are cumulative. If you have a higher version, the fix is included.

yes, this is the boot loader. I've never seen such a high value.

@SanicHegehog share the CBS folder from C:\Windows\logs

in this case you have a newer version of th kernel and the Update is no longer needed. I requested better error message since Vista, but MS ignores this.

please try this hotfix: Update to remove memory management flush serialization for all file system drivers in Window http://support.microsoft.com/kb/2981965/en-us Now the operations should run in parallel. See if this improves your disk performance.

I have Windows Live Mail crashes since August update. MS currently checks the dmps. Otherwise I have no new issues.

btw, with the Update 4 for the VS2013, Microsoft includes a GPU Usage Tool. MAybe this helps you to analyze the Dll: GPU Usage tool in Visual Studio 2013 Update 4 CTP1 http://blogs.msdn.com/b/vcblog/archive/2014/09/05/gpu-usage-tool-in-visual-studio-2013-update-4-ctp1.aspx

now I can request a new key. So the issue is fixed.

I have this, too. 30days are over.

wait for nuhi's new tool: http://www.msfn.org/board/topic/172299-the-upcoming-new-tool-for-win-78-my-suggested-name-nlitex/

without the error code we have no clue what fails Also share the folder C:\Windows\logs\CBS and the file C:\Windows\WindowsUpdate.log

provide a new xperf trace file after changing to AHCI. Also check the SMART values of your HDD

till 512µs it is still ok. Values over 1024 are bad and cause drops.

provide a xperf trace: http://www.msfn.org/board/index.php?showtopic=140264