Hi.
With changes made in upcoming v2, current beta version is showing this error:
"The service cannot be started, either because it is disabled or because it has no enabled devices associated with it"
But... this happens on my heavily modified Windows 10 x64 install with many services removed, components not installed, etc. On a vanilla Windows 10 x64 the error doesn't happen.
I don't know what may be causing this. Maybe is the new SQLite database? I have no idea. And while I understand the problem might be just on my side, I suppose it would be useful to find out what's producing this because it might affect someone out there.
Are there any steps I can follow to find where the problem is, or to generate a report a more knowledgeable person may review it?
Thank you!
I also have an issue, can't even start foobar2000 v2 Beta 2 with the following error message:
There are no more endpoints available from the endpoint mapper
Checked this error message and tried some recommended fixes but without success.
@Peter, can you tell us what are the new required dependencies to run foobar2000 v2 Beta 2?
The latest stable foobar2000 v1.6.12 final runs without problems...
-TT
I have a old 32 bit Win 10 installation on an old, maybe 15 years old Intel quad-core, ca 6.000 albums.
Latest Foobar 1 opens in ca 10 seconds, Foobar 2 needs nearly a minute to start. In this minute it's not responding.
What's strange as well is that absolutely all components are greyed out and can't be removed from inside Foobar...
Could we stop hijacking threads?
My question and TT's are somewhat related as maybe an answer with a list of required dependencies or something resembling that would be useful to find where each of our problem may reside.
I don't see how the other post has ANYTHING to do with these so why don't post it on your own thread and keep this one on topic, Alexander?
Well I did not try it out yet because atm I'm kinda busy myself, but you can try Dependency Walker (http://www.dependencywalker.com) either 32bit or 64bit depends what foobar2000 you've installed.
I see that sqlite3.dll is new in fb2k v2 and you can load it in Dependency Walker, this will list all the required Windows dll's we will need.
Open your original Windows 10 ISO and open install.wim with 7zip and put those required files back into your Windows directories.
Restart and if it does not help, try to register with regsvr32 all those dll's and restart your computer.
@bokeron, if some required Windows services are removed, it won't look good...
But you can try right click on your Windows icon in taskbar > run > type 'services.msc' and try to start all disabled and manual services that are not running.
-TT
I think Peter is too busy to ever visit threads like this. I don't have very warm feelings towards OS mutilations either.
All dependencies the player has are bundled with the installer: Visual C libraries and Universal C Runtime. Microsoft does not document their API functions telling what piece of OS is used behind the scenes.
The missing service issue is probably easily visible with Process Monitor. No idea about TT's issue, but I'd debug it with Process Monitor and possibly Process Explorer too.
At least this time your OS customizations didn't cause false alerts in crash logger. That's good.
@Alexander Ostuni : you probably have components accessing metadb with old APIs. Those are slow in foobar2000 v2.0 and that fact has been mentioned in the release notes. Also that is entirely off topic for this thread.
Hi
@Case,
thanks for mentioning Process Monitor, totally forgot about it. Can you or other users show us the processes that foobar2000.exe is using?
In Process Monitor, click on Process Tree icon:
(https://www.technewstoday.com/wp-content/uploads/2022/06/process-tree-1.jpg)
Then find foobar2000.exe and click on the "Include Process" button and in the main window, right click on the first entry ( Process start ) foobar2000.exe > Properties. Stack tab.
Can you post screenshots of all the processes?
This would help, thanks!
-TT
Thanks
@TT and
@Case I know 'mutilated' OS can be a mess. I've been modifying my installs since Win95. I was able to run WinXP smoothly on a 486 because of it. With this I mean my OSes can run almost any software I throw at them... but sometimes I need to accept some compromises which may cause a problem eventually. This seems to be the case.
I am trying to reduce the list of possible sources of error, so I asked for help here hoping to find what's changed from 1.6.x to 2.x because I don't see why what's listed in the changelog may cause this error. If no one can provide further data I suppose I'll also need to go and inspect processes, files accessed, reg keys, etc.
I once had a problem with a program which wasn't working because a chinese nls file wasn't present... and the program didn't even offered chinese as a language. Go figure.
Then find foobar2000.exe and click on the "Include Process" button and in the main window, right click on the first entry ( Process start ) foobar2000.exe > Properties. Stack tab. Can you post screenshots of all the processes?
This won't help. All it shows is access to ntoskrnl.exe and unknown modules.
I was thinking that you people would use Process Monitor to see what is attempted to be accessed and see where things error out.
But here's a list of modules loaded by clean portable foobar2000 v2.0 beta 3 x86 edition from Process Explorer:
Process: foobar2000.exe
Name Description Company Name Path
GdiPlus.dll Microsoft GDI+ Microsoft Corporation C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.22000.675_none_1631a6712776d946\GdiPlus.dll
comctl32.dll Käyttäjäkokemus-ohjausobjektien kirjasto Microsoft Corporation C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.22000.120_none_e541a94fcce8ed6d\comctl32.dll
xmllite.dll Microsoft XmlLite Library Microsoft Corporation C:\Windows\SysWOW64\xmllite.dll
wldp.dll Windows Lockdown Policy Microsoft Corporation C:\Windows\SysWOW64\wldp.dll
WinTypes.dll Windows Base Types DLL Microsoft Corporation C:\Windows\SysWOW64\WinTypes.dll
wintrust.dll Microsoft Trust Verification APIs Microsoft Corporation C:\Windows\SysWOW64\wintrust.dll
winmm.dll MCI API DLL Microsoft Corporation C:\Windows\SysWOW64\winmm.dll
winhttp.dll Windows HTTP Services Microsoft Corporation C:\Windows\SysWOW64\winhttp.dll
Windows.UI.dll Windows Runtime UI Foundation DLL Microsoft Corporation C:\Windows\SysWOW64\Windows.UI.dll
windows.storage.dll Microsoft WinRT Storage API Microsoft Corporation C:\Windows\SysWOW64\windows.storage.dll
Windows.Media.Playback.ProxyStub.dll BackgroundMediaPlayer Proxy Stub DLL Microsoft Corporation C:\Windows\SysWOW64\Windows.Media.Playback.ProxyStub.dll
Windows.Media.Playback.BackgroundMediaPlayer.dll Windows Media Playback BackgroundMediaPlayer DLL Microsoft Corporation C:\Windows\SysWOW64\Windows.Media.Playback.BackgroundMediaPlayer.dll
Windows.Media.MediaControl.dll Windows Runtime MediaControl server DLL Microsoft Corporation C:\Windows\SysWOW64\Windows.Media.MediaControl.dll
Windows.Media.Devices.dll Windows Runtime media device server DLL Microsoft Corporation C:\Windows\SysWOW64\Windows.Media.Devices.dll
win32u.dll Win32u Microsoft Corporation C:\Windows\SysWOW64\win32u.dll
version.dll Version Checking and File Installation Libraries Microsoft Corporation C:\Windows\SysWOW64\version.dll
uxtheme.dll Microsoft UxTheme Library Microsoft Corporation C:\Windows\SysWOW64\uxtheme.dll
user32.dll Yhteiskäyttö-Windows USER API Client -DLL-kirjasto Microsoft Corporation C:\Windows\SysWOW64\user32.dll
umpdc.dll User Mode Power Dependency Coordinator Microsoft Corporation C:\Windows\SysWOW64\umpdc.dll
ucrtbase.dll Microsoft® C Runtime Library Microsoft Corporation C:\Windows\SysWOW64\ucrtbase.dll
twinapi.appcore.dll twinapi.appcore Microsoft Corporation C:\Windows\SysWOW64\twinapi.appcore.dll
TextShaping.dll C:\Windows\SysWOW64\TextShaping.dll
TextInputFramework.dll "TextInputFramework.DYNLINK" Microsoft Corporation C:\Windows\SysWOW64\TextInputFramework.dll
sspicli.dll Security Support Provider Interface Microsoft Corporation C:\Windows\SysWOW64\sspicli.dll
shlwapi.dll Shell Light-weight Utility Library Microsoft Corporation C:\Windows\SysWOW64\shlwapi.dll
shell32.dll Windows Shell Common Dll Microsoft Corporation C:\Windows\SysWOW64\shell32.dll
SHCore.dll SHCORE Microsoft Corporation C:\Windows\SysWOW64\SHCore.dll
secur32.dll Security Support Provider Interface Microsoft Corporation C:\Windows\SysWOW64\secur32.dll
sechost.dll Host for SCM/SDDL/LSA Lookup APIs Microsoft Corporation C:\Windows\SysWOW64\sechost.dll
RTWorkQ.dll Realtime WorkQueue DLL Microsoft Corporation C:\Windows\SysWOW64\RTWorkQ.dll
rsaenh.dll Microsoft Enhanced Cryptographic Provider Microsoft Corporation C:\Windows\SysWOW64\rsaenh.dll
rpcrt4.dll Remote Procedure Call Runtime Microsoft Corporation C:\Windows\SysWOW64\rpcrt4.dll
powrprof.dll Power Profile Helper DLL Microsoft Corporation C:\Windows\SysWOW64\powrprof.dll
OneCoreUAPCommonProxyStub.dll OneCoreUAP Common Proxy Stub Microsoft Corporation C:\Windows\SysWOW64\OneCoreUAPCommonProxyStub.dll
oleaut32.dll OLEAUT32.DLL Microsoft Corporation C:\Windows\SysWOW64\oleaut32.dll
oleaccrc.dll Active Accessibility Resource DLL Microsoft Corporation C:\Windows\SysWOW64\oleaccrc.dll
oleacc.dll Active Accessibility Core Component Microsoft Corporation C:\Windows\SysWOW64\oleacc.dll
ole32.dll Microsoft OLE for Windows Microsoft Corporation C:\Windows\SysWOW64\ole32.dll
ntmarta.dll Windows NT MARTA provider Microsoft Corporation C:\Windows\SysWOW64\ntmarta.dll
ntdll.dll NT Layer -kirjasto (DLL) Microsoft Corporation C:\Windows\SysWOW64\ntdll.dll
msvcrt.dll Windows NT CRT DLL Microsoft Corporation C:\Windows\SysWOW64\msvcrt.dll
msvcp_win.dll Microsoft® C Runtime Library Microsoft Corporation C:\Windows\SysWOW64\msvcp_win.dll
msimg32.dll GDIEXT Client DLL Microsoft Corporation C:\Windows\SysWOW64\msimg32.dll
msctf.dll MSCTF Server DLL Microsoft Corporation C:\Windows\SysWOW64\msctf.dll
msasn1.dll ASN.1 Runtime APIs Microsoft Corporation C:\Windows\SysWOW64\msasn1.dll
msacm32.dll Microsoft ACM Audio Filter Microsoft Corporation C:\Windows\SysWOW64\msacm32.dll
MMDevAPI.dll MMDevice API Microsoft Corporation C:\Windows\SysWOW64\MMDevAPI.dll
mfplat.dll Media Foundation Platform DLL Microsoft Corporation C:\Windows\SysWOW64\mfplat.dll
MFMediaEngine.dll Media Foundation Media Engine DLL Microsoft Corporation C:\Windows\SysWOW64\MFMediaEngine.dll
KernelBase.dll Windows NT BASE API Client DLL Microsoft Corporation C:\Windows\SysWOW64\KernelBase.dll
kernel32.dll Windows NT BASE API Client DLL Microsoft Corporation C:\Windows\SysWOW64\kernel32.dll
kernel.appcore.dll AppModel API Host Microsoft Corporation C:\Windows\SysWOW64\kernel.appcore.dll
imm32.dll Multi-User Windows IMM32 API Client DLL Microsoft Corporation C:\Windows\SysWOW64\imm32.dll
imagehlp.dll Windows NT Image Helper Microsoft Corporation C:\Windows\SysWOW64\imagehlp.dll
gdi32full.dll GDI Client DLL Microsoft Corporation C:\Windows\SysWOW64\gdi32full.dll
gdi32.dll GDI Client DLL Microsoft Corporation C:\Windows\SysWOW64\gdi32.dll
ExplorerFrame.dll ExplorerFrame Microsoft Corporation C:\Windows\SysWOW64\ExplorerFrame.dll
dxgi.dll DirectX Graphics Infrastructure Microsoft Corporation C:\Windows\SysWOW64\dxgi.dll
DXCore.dll DXCore Microsoft Corporation C:\Windows\SysWOW64\DXCore.dll
DWrite.dll Microsoft DirectX Typography Services Microsoft Corporation C:\Windows\SysWOW64\DWrite.dll
dwmapi.dll Microsoft Desktop Window Manager API Microsoft Corporation C:\Windows\SysWOW64\dwmapi.dll
drvstore.dll Driver Store API Microsoft Corporation C:\Windows\SysWOW64\drvstore.dll
directxdatabasehelper.dll DirectXDatabaseHelper Microsoft Corporation C:\Windows\SysWOW64\directxdatabasehelper.dll
devobj.dll Device Information Set DLL Microsoft Corporation C:\Windows\SysWOW64\devobj.dll
dbghelp.dll Windows Image Helper Microsoft Corporation C:\Windows\SysWOW64\dbghelp.dll
dbgcore.dll Windows Core Debugging Helpers Microsoft Corporation C:\Windows\SysWOW64\dbgcore.dll
DataExchange.dll Data exchange Microsoft Corporation C:\Windows\SysWOW64\DataExchange.dll
d3d11.dll Direct3D 11 Runtime Microsoft Corporation C:\Windows\SysWOW64\d3d11.dll
d2d1.dll Microsoft D2D Library Microsoft Corporation C:\Windows\SysWOW64\d2d1.dll
cryptsp.dll Cryptographic Service Provider API Microsoft Corporation C:\Windows\SysWOW64\cryptsp.dll
cryptnet.dll Crypto Network Related API Microsoft Corporation C:\Windows\SysWOW64\cryptnet.dll
cryptbase.dll Base cryptographic API DLL Microsoft Corporation C:\Windows\SysWOW64\cryptbase.dll
crypt32.dll Crypto API32 Microsoft Corporation C:\Windows\SysWOW64\crypt32.dll
CoreUIComponents.dll Microsoft Core UI Components Dll Microsoft Corporation C:\Windows\SysWOW64\CoreUIComponents.dll
CoreMessaging.dll Microsoft CoreMessaging Dll Microsoft Corporation C:\Windows\SysWOW64\CoreMessaging.dll
comdlg32.dll Common Dialogs DLL Microsoft Corporation C:\Windows\SysWOW64\comdlg32.dll
combase.dll Microsoft COM for Windows Microsoft Corporation C:\Windows\SysWOW64\combase.dll
clbcatq.dll COM+ Configuration Catalog Microsoft Corporation C:\Windows\SysWOW64\clbcatq.dll
cfgmgr32.dll Configuration Manager DLL Microsoft Corporation C:\Windows\SysWOW64\cfgmgr32.dll
bcryptprimitives.dll Windows Cryptographic Primitives Library Microsoft Corporation C:\Windows\SysWOW64\bcryptprimitives.dll
bcrypt.dll Windows Cryptographic Primitives Library (Wow64) Microsoft Corporation C:\Windows\SysWOW64\bcrypt.dll
AudioSes.dll Audio Session Microsoft Corporation C:\Windows\SysWOW64\AudioSes.dll
atlthunk.dll atlthunk.dll Microsoft Corporation C:\Windows\SysWOW64\atlthunk.dll
advapi32.dll Advanced Windows 32 Base API Microsoft Corporation C:\Windows\SysWOW64\advapi32.dll
wow64win.dll Wow64 Console and Win32 API Logging Microsoft Corporation C:\Windows\System32\wow64win.dll
wow64cpu.dll AMD64 Wow64 CPU Microsoft Corporation C:\Windows\System32\wow64cpu.dll
wow64con.dll C:\Windows\System32\wow64con.dll
wow64base.dll C:\Windows\System32\wow64base.dll
wow64.dll Win32 Emulation on NT64 Microsoft Corporation C:\Windows\System32\wow64.dll
ntdll.dll NT Layer -kirjasto (DLL) Microsoft Corporation C:\Windows\System32\ntdll.dll
locale.nls C:\Windows\System32\locale.nls
l_intl.nls C:\Windows\System32\l_intl.nls
l_intl.nls C:\Windows\System32\l_intl.nls
l_intl.nls C:\Windows\System32\l_intl.nls
nvwgf2um.dll NVIDIA D3D10 Driver, Version 516.94 NVIDIA Corporation C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_47917a79b8c7fd22\nvwgf2um.dll
nvldumd.dll NVIDIA Driver Loader, Version 516.94 NVIDIA Corporation C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_47917a79b8c7fd22\nvldumd.dll
C_437.NLS C:\Windows\System32\C_437.NLS
C_437.NLS C:\Windows\System32\C_437.NLS
C_437.NLS C:\Windows\System32\C_437.NLS
C_1252.NLS C:\Windows\System32\C_1252.NLS
C_1252.NLS C:\Windows\System32\C_1252.NLS
C_1252.NLS C:\Windows\System32\C_1252.NLS
R00000000000d.clb C:\Windows\Registration\R00000000000d.clb
SortDefault.nls C:\Windows\Globalization\Sorting\SortDefault.nls
StaticCache.dat C:\Windows\Fonts\StaticCache.dat
zlib1.dll zlib data compression library C:\foobar2000\zlib1.dll
vcruntime140.dll Microsoft® C Runtime Library Microsoft Corporation C:\foobar2000\vcruntime140.dll
vccorlib140.dll Microsoft ® VC WinRT core library Microsoft Corporation C:\foobar2000\vccorlib140.dll
sqlite3.dll C:\foobar2000\sqlite3.dll
shared.dll C:\foobar2000\shared.dll
PP-UWP-Interop.dll C:\foobar2000\PP-UWP-Interop.dll
msvcp140.dll Microsoft® C Runtime Library Microsoft Corporation C:\foobar2000\msvcp140.dll
foobar2000.exe foobar2000 Piotr Pawlowski C:\foobar2000\foobar2000.exe
foo_unpack.dll C:\foobar2000\components\foo_unpack.dll
foo_ui_std.dll C:\foobar2000\components\foo_ui_std.dll
foo_input_std.dll C:\foobar2000\components\foo_input_std.dll
foo_freedb2.dll C:\foobar2000\components\foo_freedb2.dll
foo_fileops.dll C:\foobar2000\components\foo_fileops.dll
foo_dsp_std.dll C:\foobar2000\components\foo_dsp_std.dll
foo_dsp_eq.dll C:\foobar2000\components\foo_dsp_eq.dll
foo_converter.dll C:\foobar2000\components\foo_converter.dll
avutil-fb2k-57.dll C:\foobar2000\avutil-fb2k-57.dll
avformat-fb2k-59.dll C:\foobar2000\avformat-fb2k-59.dll
avcodec-fb2k-59.dll C:\foobar2000\avcodec-fb2k-59.dll
bd8b4b2ad74af09d151937056a19ca7a_fce8395c8fd8a99d_7722d676042ef356_0_0.0.toc %localappdata%\NVIDIA\DXCache\bd8b4b2ad74af09d151937056a19ca7a_fce8395c8fd8a99d_7722d676042ef356_0_0.0.toc
bd8b4b2ad74af09d151937056a19ca7a_fce8395c8fd8a99d_7722d676042ef356_0_0.0.bin %localappdata%\NVIDIA\DXCache\bd8b4b2ad74af09d151937056a19ca7a_fce8395c8fd8a99d_7722d676042ef356_0_0.0.bin
crypt32.dll.mui Crypto API32 Microsoft Corporation C:\Program Files\WindowsApps\Microsoft.LanguageExperiencePackfi-FI_22000.23.103.0_neutral__8wekyb3d8bbwe\Windows\System32\fi-FI\c85646935ba325e4f60b4f1a293c24c7\crypt32.dll.mui
KernelBase.dll.mui Windows NT BASE APIn asiakas-DLL Microsoft Corporation C:\Program Files\WindowsApps\Microsoft.LanguageExperiencePackfi-FI_22000.23.103.0_neutral__8wekyb3d8bbwe\Windows\System32\fi-FI\a7c1941e6709c10ab525083b61805316\KernelBase.dll.mui
PS. This OS altering really is pointless. You save some megabytes of disk space by eliminating "useless" files but it won't make the OS run faster, unless you really only have hundreds of megabytes of memory and every bit counts. The services that aren't needed consume no processing power.
PS. This OS altering really is pointless. You save some megabytes of disk space by eliminating "useless" files but it won't make the OS run faster, unless you really only have hundreds of megabytes of memory and every bit counts. The services that aren't needed consume no processing power.
Thanks for the list. I'm already trying different approaches. If something comes up I'll report back in case my results are useful for someone.
Regarding the quoted text, though offtopic, I'd like to comment a bit on this.
It does make the OS run "lighter". I don't need literally several hundreds of features Windows installs wether you need them or not. Many of them are processes considered essential... which aren't... and are running constantly, or checking periodically, transferring data, reporting... this uses disk access time, RAM and CPU cycles. Other just use disk space.
For whatever the reason, my OSes don't hang, don't bluescreen, and when some failure occur, they behave in a less catastrophical way than what you experience in a full Windows install. It's been like this for 20+ years.
Windows has come a long way, and hardware too. The impact on a modern system isn't as significative today as it was on the past... but still, in a 1TB SSD, if I can save 10gb that's 10gb more I have for some other things I do need. Having 64gb of RAM I don't really notice a few hundred Mb more or less for core Windows functionality. My Ryzen 5900x is powerful enough to run whatever Windows desires to run.
But, in the end, it's a "philosophical stance" - I prefer my OSes "Lean and Clean". I'd love to see a "modular" Windows, like Linux can still be today.
It is getting harder to achieve, and I'm growing tired of how each new Windows version tries to force more and more "functionality" on me which in the end I do not need or care for. I'd run only Linux if I didn't need full-performance for some Windows-only software.
First, even if it is not going to be supported, then these sudden compatibility shifts can tell whether applications are using OS components there is no good reason for them to use. In the very least, that is worth reporting for the exercise of debugging.
I do not know how Windows 10 and 11 behave on this matter, but earlier Windows versions provided for removing components. My previous "music computer" was a fanless Dell Mini with a total of 4 GB storage. Obviously the bundled Windows version was trimmed down. If the application's requirements for sheer computing power are satisfied, then a "for Windows but not on Dell Windows" would be a bugware warning.
these sudden compatibility shifts can tell whether applications are using OS components there is no good reason for them to use. In the very least, that is worth reporting for the exercise of debugging.
This was the other reason I had to start this thread - besides what affects me personally because my OS "mutilation".
I understand a change in the "innards" of fb2k may change software requeriments, though. There may be - there surely is- a valid reason for this.
My reasoning was... out there people have an unpredictably wide array of OS changes made by themselves or OEMs. It wouldn't hurt to find what causes this to my OS because it might affect someone else who didn't even change a thing on their PC but their Windows differ in exactly the same problem-triggering element.
I prefer my OSes "Lean and Clean". I'd love to see a "modular" Windows, like Linux can still be today.
It is getting harder to achieve, and I'm growing tired of how each new Windows version tries to force more and more "functionality" on me which in the end I do not need or care for. I'd run only Linux if I didn't need full-performance for some Windows-only software.
Here here. I've been trying to make the switch to exclusively Linux, but the fact is there's too much I use I can only run in Windows (and now that includes FB2K!). It would be easier for somebody starting out if they didn't spend decades getting skilled with Windows tools. So far as new Windows versions are concerned, I refuse to shift from Win7!
My previous "music computer" was a fanless Dell Mini with a total of 4 GB storage. Obviously the bundled Windows version was trimmed down.
My music computer is a netbook running Win7 Starter. I've acquired another as a spare!
OK, now back on topic.
On a vanilla Windows 10 x64 install I've disabled all but 20 services of the 256 that exist, and it could be just 18 if Windows Defender were not so... defensive... The system is not very functional as it is but the important point here is that...
... FB2K still runs!
Most of the services left are essential to windows working at all, so disabling one more the system fails one way or another.
All those services exist, and work, on my modified install.
There are two services, Application Information (Appinfo) and State Repository Service (StateRepository) that do prevent FB2K from launching if disabled.
On my modified Windows install, those services are also present and working.
I don't know what to make out of this.
EDIT: Using Process Explorer, all DLLs used by foobar2000.exe in vanilla Windows are also present in modified Windows.
I still don't know what to make out of this.
I don't know what to make out of this.
I once had a problem with a program which wasn't working because a chinese nls file wasn't present... and the program didn't even offered chinese as a language. Go figure.
Looks like stopping unnecessary services is not the only thing that you did to your OS
@bokeron I disabled things like telemetry or minimize it to the most basic level allowed and beef up security as far as Windows is concerned. I customize with Group Policy Editor my OS so nothing can change my wallpaper or start adding annoying system sounds. I've never had problems with my desktop apps unless it was poorly written that it crashes for just about everyone in the world that uses it or poorly documented to the point I can't figure out how to actually use it. System restore is on and I use Windows sandbox to test some stuff out with apps.
I use a clean install of Windows with the appropriate device drivers as a base at the OS level that's easily updatable. No OEM preinstalled crap here. Avoid over customizing Windows as it give you hell. Stick close to stock.
The user folders are kind of safe to manually clean up if you know what you're doing. Program Files less so. The Windows folder and other system folders even way less so. Generally you don't need to clean out a system unless you uninstall an app or want to get rid of temporary files after finishing a massive project or updating a bunch of apps manually. You can do an upgrade in place to clean up some left over crap from feature updates long ago but that carries risks, too.
Bottom line: Don't over do it because you can break it and will need a full reinstall to fix.
Looks like stopping unnecessary services is not the only thing that you did to your OS
Maybe I need to clarify it again. Starting from a vanilla Windows 10 x64 I have:
OS 1: Install size 5.34GB, RAM used 0.7GB
Heavily modified OS. And I mean heavily. Services aren't only stopped but removed. Packages removed using DISM. Lots of features removed with most of their files unless they're needed for anything else. Too long to explain it here.
This OS runs "everything" just fine. FB2K 1.6.x, Premiere, Lightroom, InDesign, Photoshop, Illustrator, Ableton Live, Software synths, Microsoft Office, VMware Workstation, VueScan, Krita, KiCAD, Python, Matlab, Android Studio, Cadence AWR and Virtuoso, etcetera...
I test all the software I need before deploying the OS.
OS 2: Install size, 19.1GB, RAM used 1.5GB
Vanilla Windows install
OS 1 can't run new FB2K 2.0, though. I'm just trying to find why.
This is the one that failed ONE TIME, 6 years ago, because of an nls file.
OS 2 can run FB2K 2.0, and when I'm writing I've stopped every service but 20 I'm referring to this OS. And I disabled them to test if any of them was needed for the new FB2K version so I could find something useful trying to solve the problem with OS 1.
PS:
@Chibisteven thanks for your message but, as I've said before, I've been doing this for 20+ years. I know Windows quite well... though I can't find why FB2K 2.0 won't run LOL.
@bokeron,
finally had some time to debug this problem and I bring good news.
I know where the problem is and what we ( at least for me it's working ) need to make fb2k v2 work.
First I need to make a new Windows image and make some final testing.
My Win10x64 ISO is only 980 MB and 3.95 GB installed 8) and yea I've been slimming my Windows since XP too...
-TT
@bokeron,
finally had some time to debug this problem and I bring good news.
I know where the problem is and what we ( at least for me it's working ) need to make fb2k v2 work.
First I need to make a new Windows image and make some final testing.
My Win10x64 ISO is only 980 MB and 3.95 GB installed 8) and yea I've been slimming my Windows since XP too...
-TT
Great news. I hope you can solve it on your end.
If I'm lucky your solution might solve my problem too, or at least throw some light on the matter.
Got it working,
here is the minimum list of Windows services you need to have running:
Application Information
Background Task Infrastructure
Base Filtering Engine
CoreMessaging
DCOM Server Process Launcher
DHCP Client
DNS Client
Group Policy Client
Local Session Manager
Network List Service
Network Location Awareness
Network Store Interface Service
Power
Radio Managment Service
Remote Procedure Call (RPC)
RPC Endpoint Mapper
Security Accounts Manager
System Events Broker
Task Scheduler
User Manager
User Profile Service
Windows Defender Firewall
Windows Event log
The new fb2k v2 needs to have two additional services/dll's, do not completely remove nor disable:
Application Information (Appinfo) > System32\appinfo.dll
If the service is not running, you will get the error message: The interface is unknown.
The Appinfo service is also linked to User Account Control (UAC) so don't remove UAC completely.I have set this service to manual start.
Connected Devices Platform Service (CDPSvc) > System32\CDPSvc.dll
Connected Devices Platform User Service (CDPUserSvc) > System32\CDPUserSvc.dll
These two are linked to Remote Procedure Call (RPC) and RPC Endpoint Mapper.
I have set those two services to manual start.
That's it, I hope it helps for other people.
-TT
@TT Good for you! Glad you solved it.
On my side things look different.
All the services you mention except the two "Connected Devices Platform" are present, enabled and running on my modified OS.
So, this might be the cause of the problem.
BUT
On my non-modified OS, where FB2K works OK, I tested disabling a lot of services as I've said somewhere before.
The funny thing is... of all services you mentioned, I have DISABLED these:
Base Filtering Engine
DHCP Client
DNS Client
Network List Service
Network Location Awareness
Network Store Interface Service
Power
Radio Managment Service
Task Scheduler
Windows Defender Firewall
Connected Devices Platform Service
Connected Devices Platform User Service
And FB2K still works.
And, apart from this... why on earth would FB2K be so dependant on those 2 services and the Connected Devices Platform, which is useful to some but in no way is essential and shouldn't be treated as that?
The list I've posted is the minimum without completely breaking the OS.
I think you can after post-install ( but not before, because it breaks Windows installation ) remove the Windows Firewall,
I'm using the Comodo Firewall anyways.
You definitely need:
Application Information (Appinfo) > System32\appinfo.dll, without it you get error message: The interface is unknown.
Connected Devices Platform Service (CDPSvc) > System32\CDPSvc.dll
Connected Devices Platform User Service (CDPUserSvc) > System32\CDPUserSvc.dll
Remote Procedure Call (RPC)
RPC Endpoint Mapper
User Manager, without it you get error message: The interface is unknown.
I guess in the new fb2k v2 version, there is a new remote control option and maybe some new streaming option,
that's why you need the RPC and the other services that are linked and communicating with each other.
My problem was, that I have completely removed UAC that also removed Application Information. This was needed with
the two Connected Devices Platform Service to be able communicate with the RPC service.
Btw, you can also check right click on Windows taskbar icon > Run > services.msc , the dependencies for each of these services. Right click > Properties > Dependencies tab.
-TT
You definitely need:
Application Information (Appinfo) > System32\appinfo.dll, without it you get error message: The interface is unknown.
Connected Devices Platform Service (CDPSvc) > System32\CDPSvc.dll
Connected Devices Platform User Service (CDPUserSvc) > System32\CDPUserSvc.dll
If you read my messages above, just for testing I installed a non-modified Windows 10 x64 and disabled everything but 20 services, and while Windows failed a lot, FB2K still worked. Is not a Windows to be used at all, is just an experiment.
So, what I mean is I also disabled these these 3 services I've quoted and FB2K still works, so they seem to be non-essential for FB2K on my full-install.
On the other hand, on the OS I do use, the modified one, many services aren't just disabled, they aren't installed at all, so no reg key for them, no DLLs, etcetera.
So your findings are interesting because in this OS I don't have the 2 services related to "Connected Devices Platform" - they're not disabled, they don't exist at all, no DLLs, nothing... so it might be that whatever else that isn't set up properly for these services because I removed them from the install ISO is messing withg FB2K 2.0.
And, assuming this were the case, I still don't see anything new in the changelog for 2.x that needs them. So I'm curious about why are they a requeriment now (if that's what is really happening, which I don't know).
I do think developers should put some thought on this issue we are (well, now only *I* am LOL) having, if only to pinpoint what the problem really is and conclude it is because of what I did and can't be reproduced except by nuking the OS but not by OEM modifications or something like that.
My previous "music computer" was a fanless Dell Mini with a total of 4 GB storage. Obviously the bundled Windows version was trimmed down. If the application's requirements for sheer computing power are satisfied, then a "for Windows but not on Dell Windows" would be a bugware warning.
And my
main setup is a fanless Dell Mini with just added SSD space and more RAM to force it to run MSVC2022.
I didn't need to alter it at all. Making developers cater to butchered Windows installs is insane.
My previous "music computer" was a fanless Dell Mini with a total of 4 GB storage. Obviously the bundled Windows version was trimmed down. If the application's requirements for sheer computing power are satisfied, then a "for Windows but not on Dell Windows" would be a bugware warning.
And my main setup is a fanless Dell Mini with just added SSD space and more RAM to force it to run MSVC2022.
I didn't need to alter it at all. Making developers cater to butchered Windows installs is insane.
Who is asking for that?
In my own case, I just need help to pinpoint why is failing for me so I can make modifications to my OS to run FB2K again. Why is everyone here so defensive?
In the case you quote, is the OEM who "butchers" the OS. So your answer means you don't care if your software runs in a commercial and licensed product.
Maybe the questions you should be making are...
1. What have we changed that makes the new version to fail on a licensed OEM Windows?
2. Do we really need to do it that way or can we offer the same functionality without causing issues on licensed OEM installs?
3. Can we at least indicate what is required to run the software to those users who bought a commercial licensed product?
I need to take a stance and get some things right, because the comments and remarks here are quite shocking to be quite honest.
"Mutilated OS" or "Butchered OS" this is quite ironic, because the original Windows is and always will be a "Mutilated OS" or "Butchered OS", it is quite a sad story.
The entire Windows OS is a bugware/bloatware/malware/spyware system and everybody knows it, but most people do not want to talk about it.
There must be quite a few reasons why serious companies, intelligence agencies, military, IPS/Server hosting, hackers etc, etc do not use Windows. Why?
Because Windows is a joke targeted for the mainstream, it can be said it's just a Gamer OS... I can remember the news and memes where british nuclear submarines have used Windows for their OS,
let's hope it did not crash on some critical situations, it would have not been public anyways :)
Here in this thread, there where some talks about slimming Windows down does not have any effect on performance, you really can't be serious about these statements, this is just trolling.
So an original 5.5 GB Windows ISO is the same as a 980 MB ISO? A 20 GB installed Windows has the same performance as a 4 GB installed Windows?
The same analogy would be to state a 100 kg sprinter is as fast as a 60 kg sprinter.
I have some news for you, my "mutilated" and "butchered" Windows boots on an 14 year old computer in 15 seconds where the original Windows needs 35 seconds!
Not only that, the performance is super smooth, snappy, fast, clean and stable. It's only 10-15% slower than Unix based distros.
On the other hand, original Windows is so slow, lags, loads, calls home etc, etc.
I can't even install original Win10/Win11 on my old laptop because it requires so much resources...
Why? Because of malware, because of useless services running, because of telemetry ( did you check with TCPView the connections ? I have 0 connections to MS server ) because of bad and useless programs etc, etc.
On the other hand, I can install my customized Windows 10 on my old laptop that has only 1 GB Ram!
So what is the business plan for Microsoft to run their Windows acceptable smoothly? That's a really easy answer, just buy
the right hardware and you're good to go, gamers do that anyways! Let's not even talk about the Windows update/bugfix patch hell, it was and it is ridiculous and always will be, that says a lot...
All I can say is that not ALL people want such a bad Windows and also want to value their privacy, that's why customization comes into play.
It is the same philosophy and mentality like Unix based systems where based off. Clean, fast, small footprint, secure, no bloatware/spyware etc.
Let's be honest, most people are just lazy, they don't to know or don't want to try new things out, new better alternatives that are even free.
What is the percentage of Windows user that even tried Linux in their lifetime? For starters and Windows users, who are drag n drop and click users, you can try the PCLinuxOs distro,
really easy to learn for a first Linux experience or for advanced folks you can try Artix Linux which is super clean and build it as you need.
Btw, I can run all the programs ( 200+ ) I need and yes of course there are "some" exceptions ( like this new fb2k v2 ) over the last 20 years where I needed to fix some things myself, but this is not a big deal.
There are some general rules what you can and can not remove to have a compatible and stable system, but through experience you will learn that. So next time, could you please not to disencourage other users?
And last before you ask, yes I would long long time ago completely switch to Linux but there are "some" programs I need for work and don't want to have emulated Windows programs in Linux...
That's all I have to say, thanks for reading.
P.S
@bokeron, I hope that you can fix your issue, good luck.
-TT
Regarding what
@TT has just posted, I need to add a remark.
@mudlord quoted a person explaining his Dell is having a problem because of the OFFICIAL OS that came with it.
If mudlord were the one having the problem with his own Dell and couldn't be solved by just adding RAM and SSD then maybe he'd see things differently.
So, one last time: This is not about
@TT or me. We can manage this, and solve it, though we asked for help and we got offered almost none. This is about a common user out there who doesn't know why he can't use his/her favorite player, foobar2000.
If you don't care about such a user and are just gonna tell him/her to use any other player, then why publisdh foobar2000 at all? Keep it for yourselves. How many developers would you think this program had if it were not because we are so many users??
Really, the stubborness in this forum is maddening.
And now... * I've solved the problem on my end. *
The solution begets a big question:
Why on earth must a program that isn't downloaded via Microsoft Store REQUIRE appxsvc and clipsvc to be enabled and running?????
Previous versions can be downloaded from MS Store and from FB2K home page and aren't so restrictive.
And now... * I've solved the problem on my end. *
The solution begets a big question:
Why on earth must a program that isn't downloaded via Microsoft Store REQUIRE appxsvc and clipsvc to be enabled and running?????
Previous versions can be downloaded from MS Store and from FB2K home page and aren't so restrictive.
I don't know? Maybe because it's actually on the Windows store and a possible requirement by Microsoft? 😒
Enable the services and be done with it then or stick with 1.6. Your choice. 😒
And now... * I've solved the problem on my end. *
The solution begets a big question:
Why on earth must a program that isn't downloaded via Microsoft Store REQUIRE appxsvc and clipsvc to be enabled and running?????
Previous versions can be downloaded from MS Store and from FB2K home page and aren't so restrictive.
I don't know? Maybe because it's actually on the Windows store and a possible requirement by Microsoft? 😒
Enable the services and be done with it then or stick with 1.6. Your choice. 😒
1.6 is available at MS Store but when I download it from its home page I can run it without those two services. So explain me why the sarcasm? Does MS prevent fb2k 2.0 from working just like 1.6 regarding this?
Yep. The usual answer around here. Screw the users, we know better.
I can activate the services but what about those who can't because their OEM has disaled or purged them? Screw them too?
I still don't know why I insist on making this a better program when no one seems to care. Nobody needed or wanted dark mode and now it's being done. Maybe I am right on this one, too -- there's no need to make those services a requeriment if I'm not downloading from MS Store.
I've never found a more obnoxiously arogant fanbase than this.
Nobody needed or wanted dark mode and now it's being done.
Hilarious.
(https://i.imgur.com/lR5ywQX.png)
(https://pbs.twimg.com/media/DxUp8K2VYAAbyE7?format=jpg)
I thought a while how to react to this topic initially. I was thinking about ignoring it and not provide any help, but since I replied I had to also voice my experience that this kind of altering is pointless. And it's mutilation since it breaks software.
Claiming that OEM customizations could also be affected is simply incorrect. They use official supported methods to add logos and bloatware, nothing more.
I would like to test the performance of your customized OS. For now I tested 64-bit Tiny10 that I found with little effort.
I compared Tiny10, Regular Windows 10 and Windows 10 where I uninstalled OneDrive, disabled Defender and CEIP tasks and turned off Meltdown and Spectre mitigations.
Tiny10 requires 10 GB less disk space.
Tiny10 uses 1 GB memory. Official uses 1.4 GB. Tweaked 1.2 GB.
Tiny10 boots to desktop in 11.44 s. Regular in 11.82 s. Tweaked in 10.6 s.
Tiny10 starts my customized foobar2000 instantly after boot in 0:00.344889. Regular in 0:01.101058. Tweaked in 0:00.318430.
Regular is the only one with antivirus running, that makes it the slowest.
Tiny10 has no Store so it can't use any Microsoft provided codec additions or run proper Netflix app with all features enabled. Not to mention any other handy software found from Store.
This Tiny10 didn't win a mostly stock OS in any benchmark that mattered to me. It only uses a little less disk usage. I rather have my fully functional OS than shave any GBs off install size.
So explain me why the sarcasm?
I'm beginning to get quite annoyed with you. It's not sarcasm. 😒
Nobody needed or wanted dark mode and now it's being done.
Well??? Another user just pointed this out:
(https://i.imgur.com/lR5ywQX.png)
@bokeron Why don't you figure what you really want? I mean as long as it isn't drama or you changing your mind. You can stop gaslighting us now. You got your dark mode and now you want to whine about Microsoft when the actual product you're trying to use is in beta anyway on a operating system installation that you messed up. Dude, see a doctor for that condition of yours. What is wrong with you?
It's blatantly obvious to people with actual knowledge and experience that you have no idea what you're doing, and you can cite no valid or useful data points to your imagined improvements. Your "bug" report is completely worthless, because your system is in a brain damaged state caused by yourself. You're wasting everyone's time, including your own.
Nobody needed or wanted dark mode and now it's being done.
Hilarious.
(https://i.imgur.com/lR5ywQX.png)
Hlarious it is.
Everytime I've asked for it, which I've done since some years ago, I've been met with contempt. But now, oh my god, it's being implemented.
It's blatantly obvious to people with actual knowledge and experience that you have no idea what you're doing, and you can cite no valid or useful data points to your imagined improvements. Your "bug" report is completely worthless, because your system is in a brain damaged state caused by yourself. You're wasting everyone's time, including your own.
It is blatantly obvious you lack the most elemental education, and that's why you're a moderator on the most cult-like forum on the net.
Do you think that insulting me is winning you zealot points? What are you, a 13 yo bully?
The software is beta. It still requires two services that it should not require and didn't require before. If I'm too stupid to understand it why do you insult me instead of explining me what's going on?
Is this how you answer your users? Don't answer this one, it is already clear what the answer is.